On 18 April 2017 at 08:20, Daniel Abrahamsson <hams...@gmail.com> wrote:
> I've run into a case where I got a sbiling error/response on the first > ever write to a key. I would like to understand how this could happen. > Normally when you get siblings, it is because you have written a value > with an out-of-date vclock. But since this is the first write, there > is no vclock. Could someone shed some light on this for me? > > It is worth to mention that the it took 3 seconds for Riak to deliver > the response, so it is possible there was some kind of network issue > at the time. > > Here are some details about my setup: > Number of nodes: 8. > n_val: 5 > write options: pw: 3 (quorum), return_body > > Regards, > Daniel Abrahamsson > Hi Daniel, Please let me know if all nodes in this cluster were set up completely fresh, with empty backend directories, or if any of them had been used before for a Riak installation. If the latter is the case, it may be that the key in question had already been used once before. Cluster nodes pick up data from pre-existing backends. How do you access the key for read and write operations? Kind Regards, Magnus Magnus Kessler Client Services Engineer Basho Technologies Limited Registered Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
