# Node never gets its share of the shards **URL:** \ **Category:** Elasticsearch\ **Created:** [October 10, 2011, 10:42am UTC](https://discuss.elastic.co/t/node-never-gets-its-share-of-the-shards/5549 "2011-10-10T10:42:28Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Steff](https://avatars.discourse-cdn.com/v4/letter/s/e36b37/32.png) [@Steff](https://discuss.elastic.co/u/Steff)\ **Post date:** [October 10, 2011, 10:42am UTC](https://discuss.elastic.co/t/node-never-gets-its-share-of-the-shards/5549/1 "2011-10-10T10:42:28Z")
Hi I have a simple setup with four ES nodes (192.168.88.140-143) in cluster. The nodes are started at almost the same time and shortly after client nodes are started. The client nodes create one index with 12 shards (and 1 replica) and start indexing documents into those. It works ok. I look at the ES cluster through elasticsearch-head. I see that there are no shards assigned to one of the nodes (the one at 192.168.88.140), and that node appear on a yellow background in elasticsearch-head - the other 3 nodes appear on a white background. Besides that I do not notice any problem with 192.168.88.140, would explain why it does not get shards assigned. Can anyone help explain why 192.168.88.140 does not get its fair share of the shards? Regards, Per Steffensen ---
**Author:** ![Thibaut\_Britz](https://avatars.discourse-cdn.com/v4/letter/t/a6a055/32.png) [@Thibaut\_Britz](https://discuss.elastic.co/u/Thibaut_Britz)\ **Post date:** [October 10, 2011, 10:48am UTC](https://discuss.elastic.co/t/node-never-gets-its-share-of-the-shards/5549/2 "2011-10-10T10:48:55Z")
That's your master node. You probably have: node.master: true node.data: false in the configuration file for that node. Thibaut On Mon, Oct 10, 2011 at 12:42 PM, Steff [steff@designware.dk](mailto:steff@designware.dk) wrote: > Hi > > I have a simple setup with four ES nodes (192.168.88.140-143) in > cluster. The nodes are started at almost the same time and shortly > after client nodes are started. The client nodes create one index with > 12 shards (and 1 replica) and start indexing documents into those. It > works ok. > > I look at the ES cluster through elasticsearch-head. I see that there > are no shards assigned to one of the nodes (the one at > 192.168.88.140), and that node appear on a yellow background in > elasticsearch-head - the other 3 nodes appear on a white background. > Besides that I do not notice any problem with 192.168.88.140, would > explain why it does not get shards assigned. > > Can anyone help explain why 192.168.88.140 does not get its fair share > of the shards? > > Regards, Per Steffensen ---
**Author:** ![Steff](https://avatars.discourse-cdn.com/v4/letter/s/e36b37/32.png) [@Steff](https://discuss.elastic.co/u/Steff)\ **Post date:** [October 10, 2011, 11:52am UTC](https://discuss.elastic.co/t/node-never-gets-its-share-of-the-shards/5549/3 "2011-10-10T11:52:32Z")
On 10 Okt., 12:48, Thibaut Britz [thibaut.br...@trendiction.com](mailto:thibaut.br...@trendiction.com) wrote: > That's your master node. You probably have: > > node.master: true > node.data: false > > in the configuration file for that node. Nope. I have the same config, saying nothing about node.master or node.data, for all 4 nodes. I hope (for the sake of HA) that you do not have to point out a master in a config file. I should also say that sometimes when I start the same simple test in the same simple setup, all four nodes gets their share of the shards. It is only sometimes that this "problem" occur. > Thibaut > > On Mon, Oct 10, 2011 at 12:42 PM, Steff [st...@designware.dk](mailto:st...@designware.dk) wrote: > > > Hi > > > I have a simple setup with four ES nodes (192.168.88.140-143) in > > cluster. The nodes are started at almost the same time and shortly > > after client nodes are started. The client nodes create one index with > > 12 shards (and 1 replica) and start indexing documents into those. It > > works ok. > > > I look at the ES cluster through elasticsearch-head. I see that there > > are no shards assigned to one of the nodes (the one at > > 192.168.88.140), and that node appear on a yellow background in > > elasticsearch-head - the other 3 nodes appear on a white background. > > Besides that I do not notice any problem with 192.168.88.140, would > > explain why it does not get shards assigned. > > > Can anyone help explain why 192.168.88.140 does not get its fair share > > of the shards? > > > Regards, Per Steffensen ---
**Author:** ![Steff](https://avatars.discourse-cdn.com/v4/letter/s/e36b37/32.png) [@Steff](https://discuss.elastic.co/u/Steff)\ **Post date:** [October 11, 2011, 7:08am UTC](https://discuss.elastic.co/t/node-never-gets-its-share-of-the-shards/5549/4 "2011-10-11T07:08:37Z")
I run without replica. The node that does not get any shards might somehow join the cluster millisecs after the index has been created and shards initially assigned (to the other nodes). Is ES able to reassign (move) shards that does not have any replica? If not, that might be the explanation?!? Regards ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [October 11, 2011, 8:50am UTC](https://discuss.elastic.co/t/node-never-gets-its-share-of-the-shards/5549/5 "2011-10-11T08:50:47Z")
On Tue, 2011-10-11 at 00:08 -0700, Steff wrote: > I run without replica. The node that does not get any shards might > somehow join the cluster millisecs after the index has been created > and shards initially assigned (to the other nodes). Is ES able to > reassign (move) shards that does not have any replica? If not, that > might be the explanation?!? ES should move shards around to rebalance the cluster. Are you absolutely sure that that node has joined the cluster? When starting a number of nodes at once, the transfer of data from one node to another can make nodes slow to respond to cluster join requests, which can cause a new node to think that it is alone and should start its own cluster. The speed of recovery can be tuned: > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. clint ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 12, 2011, 8:56pm UTC](https://discuss.elastic.co/t/node-never-gets-its-share-of-the-shards/5549/6 "2011-10-12T20:56:57Z")
Also, double check that no shards are allocated on that node using the cluster state API (on top of making sure you see in the log that the node joined the cluster). On Tue, Oct 11, 2011 at 10:50 AM, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)wrote: > On Tue, 2011-10-11 at 00:08 -0700, Steff wrote: > > > I run without replica. The node that does not get any shards might > > somehow join the cluster millisecs after the index has been created > > and shards initially assigned (to the other nodes). Is ES able to > > reassign (move) shards that does not have any replica? If not, that > > might be the explanation?!? > > ES should move shards around to rebalance the cluster. Are you > absolutely sure that that node has joined the cluster? > > When starting a number of nodes at once, the transfer of data from one > node to another can make nodes slow to respond to cluster join requests, > which can cause a new node to think that it is alone and should start > its own cluster. > > The speed of recovery can be tuned: > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/modules/cluster.html) > > clint ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:52am UTC](https://discuss.elastic.co/t/node-never-gets-its-share-of-the-shards/5549/7 "2017-07-06T03:52:14Z")