I understand there could be many reasons, but if it is at all possible, I'd suggest you upgrade to a more recent version of Solr.
With that, you'd get a ton of bug fixes, and also a bunch of APIs that would help you with triggering a leader election. On Tue, Jul 26, 2016 at 9:27 PM, Tim Chen <tim.c...@sbs.com.au> wrote: > Hi Guys, > > I am running a Solr Cloud 4.10, with 4 Solr servers and 5 Zookeeper setup. > > Solr servers: > solr01, solr02, solr03, solr04 > > I have around 20 collections in Solr cloud, and there are 4 Shards for > each Collection. For each Shard, I have 4 Replicas, and sitting on each > Solr server, with one of them is the Shard Leader. > > The issue I am having right now is all the Shard Leader are pointing to > the same server, eg: solr01. When there are documents update, they are all > pushed to the Leader. I really want to distribute the Shard Leader across > all 4 Solr servers. > > I noticed Solr 6 has a "REBALANCELEADERS" command to do that, but not > available in Solr 4. > > Questions: > > 1, Is my setup OK? with 4 Shards for each Collection and 4 Replicas for > each Shard. Each Solr server has full set of documents. > 2, To distribute the Shard Leader to different Solr servers, can I somehow > shutdown a single Replica that is currently a Shard Leader and force Solr > to elect a different replica to be new Shard Leader? > > Thanks guys! > > Regards, > Tim > > > [Roots Wednesday 27 July 8.30pm]<http://www.sbs.com.au/programs/roots/> > -- Anshum Gupta
