Query on Riak Search in a cluster of 3 nodes behind ELB is giving different result everytime

Vitaliy E 13vitamins at gmail.com
Wed Apr 1 04:06:13 EDT 2015

Hi Alex,

riak-admin member-status is the command

(N - 1) nodes were showing all N nodes as part of the cluster, but "Ring
Ready: false" at the same time. One node was showing just itself in
"risk-admin member-status". Strangely, when shut down its status was
reflected in the admin console of the cluster, but no replication was done
so I'm sure it wasn't working together with the rest of the nodes.

Repaired by joining the cluster as if it was never attempted before:

riak-admin cluster join <node>
riak-admin cluster plan
riak-admin cluster commit


On Wed, Apr 1, 2015 at 10:54 AM, Alex De la rosa <alex.rosa.box at gmail.com>

> Hi Vitaliy,
> How did you find out a node in the cluster was not part in the cluster?
> any commands to check that? And then, how did you fix that? (Just curious
> and for future references)
> Thanks,
> Alex
> On Wed, Apr 1, 2015 at 9:50 AM, Vitaliy E <13vitamins at gmail.com> wrote:
>> Hello everyone,
>> I've just joined the list, and am a bit late to the party. Sorry about
>> that. Thought I would contribute an answer anyway.
>> Santi, what is you n_val?
>> I observed the behavior you are describing on Riak 2.0.0 with n_val=3 in
>> two cases:
>> 1. One of the nodes was not part of the cluster although the cluster was
>> thinking it was. Don't ask me how that happened. Obviously, when a request
>> hit that node part of the entries could not be found there.
>> 2. Look for indexing errors in Solr console and Riak logs. Each Riak node
>> has its own Solr "repository", so if an entry fails to be indexed on any of
>> them, search results will be inconsistent depending on which set of nodes
>> returns it. Let's say you have replicas on nodes A, B, and C. Entry X
>> failed to be indexed on A, entry Y failed to be indexed on A and B, and
>> entry Z was indexed OK on all nodes. Then you may get {X,Y,Z}, {X,Z}, or
>> {Z} as your search results.
>> In our case the indexing failures were caused by disk/filesystem errors.
>> Regards,
>> Vitaly
>> _______________________________________________
>> 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/20150401/e58a77c8/attachment-0002.html>

More information about the riak-users mailing list