I wouldn't worry about it. I doubt you could even measure the change in overall cluster performance even if all three leaders were on the same node.
The REBALANCELEADERS stuff was put in for cases of having 100s of leaders on the same machine. It won't hurt, but is almost certainly completely unnecessary. Best, Erick On Thu, Dec 24, 2015 at 5:12 AM, Ishan Chattopadhyaya <ichattopadhy...@gmail.com> wrote: > Maybe, you could have a look at REBALANCELEADERS to see if this solves your > usecase? > https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-RebalanceLeaders > > On Thu, Dec 24, 2015 at 3:54 PM, <tarek.abouzei...@yahoo.com.invalid> wrote: > >> Hi guys , >> i have a solr cluster of 3 nodes using solr cloud , and a collection of 3 >> shards , below is what's seen in cloud >> Node 1 : shard1_replica1 , shard2_replica2Node 2 : shard2_replica1 >> , shard3_replica2Node 3 : shard1_replica2 , shard3_replica1 >> >> Leaders : >> Shard 1 :Node 1Shard 2 :Node 2Shard 3 :Node 1 >> i want to make shard 3's leader Node 3 to not make node 1 busy with >> leading both shard 1 and shard 3 , or solr automatically make load balance >> through the 3 nodes ? >> Thanks in advance >> -- Best Regards, >> -- Tarek Abouzeid
