N = 3 and RW = 2 not finding some keys

Bryan Hunt bryan.hunt at erlang-solutions.com
Fri May 18 06:00:24 EDT 2018

Hi Guido, 

You should attempt to change the bucket property ‘notfound_ok’ from the default of ‘true' to ‘false'.


curl -XPUT -H "Content-Type: application/json" -d '{"props":{"notfound_ok": false}}'

This makes GET operations for non-existent keys slower as it forces an internal GET for each of the three copies.

https://docs.basho.com/riak/kv/2.1.1/developing/app-guide/replication-properties/#the-implications-of-notfound-ok <https://docs.basho.com/riak/kv/2.1.1/developing/app-guide/replication-properties/#the-implications-of-notfound-ok>

From what you describe, it sounds like only a single copy (out of the original three), somehow remain present in your cluster.

Best Regards,

Bryan Hunt

> On 17 May 2018, at 15:42, Guido Medina <gmedina at temetra.com> wrote:
> Hi all,
> After some big rebalance of our cluster some keys are not found anymore unless we set R = 3, we had N = 3 and R = W = 2
> Is there any sort of repair that would correct such situation for Riak 2.2.3, this is really driving us nuts.
> Any help will be truly appreciated.
> Kind regards,
> Guido.
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20180518/4f7a587e/attachment.html>

More information about the riak-users mailing list