Hi list, unfortunately REBALANCELEADERS is not reliable and the leader election has unpredictable results with SolrCloud 6.6.5 and Zookeeper 3.4.10. Seen with 5 shards / 3 replicas.
- CLUSTERSTATUS reports all replicas (core_nodes) as state=active. - setting with ADDREPLICAPROP the property preferredLeader to other replicas - calling REBALANCELEADERS - some leaders have changed, some not. I then tried: - removing all preferredLeader properties from replicas which succeeded. - trying again REBALANCELEADERS for the rest. No success. - Shutting down nodes to force the leader to a specific replica left running. No success. - calling REBALANCELEADERS responds that the replica is inactive!!! - calling CLUSTERSTATUS reports that the replica is active!!! Also, the replica which don't want to become leader is not in the list of collections->[collection_name]->leader_elect->shard1..x->election Where is CLUSTERSTATUS getting it's state info from? Has anyone else problems with REBALANCELEADERS? I noticed that the Reference Guide writes "preferredLeader" (with capital "L") but the JAVA code has "preferredleader". Regards, Bernd
