Yes, this looks like the standard tail-wrapping problem. You are right
that adding an eight node should resolve this, and if the standard code
doesn't resolve it, running plans with v3 will eventually resolve it.
As for when the warning would appear, I'm not sure I really know when the
warning wo
Thank you, Martin! With that information plus output of `riak-admin cluster
partitions --node=...` I was able to determine which nodes have
preflist/replica problems.
Two nodes in my cluster appear to have problems. Here are the partition
mappings prior to adding the 7th node. I think things will
Daniel,
See this post (
http://lists.basho.com/pipermail/riak-users_lists.basho.com/2017-August/019488.html)
and the links in it for some more details on issues with the core claim
algorithm. The fix is in the pending release 2.2.5 which Russell is adding
the finishing touches to at the moment.
There are 2 options for that situation when riak-admin cluster plan gives
you the Not all replicas will be on distinct nodes warning.
1. You can riak-admin cluster clear, which will wipe out the plan, and the
riak-admin cluster plan again. You will get the same effect of
redistributing the vnodes
