Shawn is spot-on, here's a little bit of "color commentary" bq: all new documents to index will be routed to the same machine, thus indexing load is not subdivided
This is something of a misconception. Indexing is always done on all nodes, leaders and replicas alike in SolrCloud. The leader is responsible for coordinating the distribution of the raw documents to the followers, _not_ forwarding the _indexed_ doc. Best, Erick On Mon, Jan 11, 2016 at 8:48 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 1/11/2016 8:45 AM, Gian Maria Ricci - aka Alkampfer wrote: >> Due to the different reboot times probably, I’ve noticed that upon >> reboot all three leader shards are on a single machine. I’m expecting >> shard leaders to be distributed evenly between machines, because if >> all shard leader are on a same machine, all new documents to index >> will be routed to the same machine, thus indexing load is not subdivided. > > You're looking for the REBALANCELEADERS functionality ... but because > you only have three nodes, the fact that one machine has the leaders for > all three shards is not really a problem. > > https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-RebalanceLeaders > > This feature was added for a use case where there are hundreds of nodes > and hundreds of total shards, with the leader roles heavily concentrated > on a small number of nodes. With REBALANCELEADERS, the leader roles can > be spread more evenly around the cluster. > > It is true that the shard leader does do a small amount of extra work, > but for a very small installation like yours, the overhead is nothing to > be concerned about. You can do something about it if it bothers you, > though. > > Thanks, > Shawn >
