Description
Conditions under which the problem happens:
1) Rebalance interrupted
2) num_replicas decreased
3) Some vbuckets are in a "dead" state on some nodes
In this case ns_server:do_sanify_chain might pick FutureChain for vbucket which length is longer than the length of the original Chain which leads to vbucket map with variable chain lengths (corrupted)