Understanding read_repairs

Russell Brown russell.brown at me.com
Sun Feb 24 10:10:58 EST 2013

On 24 Feb 2013, at 15:01, Sebastian Cohnen <sebastian.cohnen at gmail.com> wrote:

> Can you confirm that the PR didn't made it into 1.3.0? It was closed about two four weeks ago...

It is not in 1.3. We actually had the code freeze for 1.3.0 a _long_ time ago (I think it was 16th Nov 2012) and this fix did not make it in time for the freeze.


> I think I'm hitting the same issue here. In one project I'm using last write wins and the read repair count is ridiculously high. I'm hoping that this might also help reducing the latency problem we are seeing for the 99th+ percentiles of requests.
> On 22.02.2013, at 09:24, Russell Brown <russell.brown at me.com> wrote:
>> It is fixed in master, but it doesn't look like it made it into 1.3.0. If you're ok with building from source, I tried it and a patch from 8895d2877576af2441bee755028df1a6cf2174c7 goes cleanly onto 1.3.0.
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

More information about the riak-users mailing list