# Status red **URL:** \ **Category:** Elasticsearch\ **Created:** [August 18, 2012, 6:27pm UTC](https://discuss.elastic.co/t/status-red/8781 "2012-08-18T18:27:42Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Marcin\_Dojwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcin_dojwa/32/2307_2.png) [@Marcin\_Dojwa](https://discuss.elastic.co/u/Marcin_Dojwa)\ **Post date:** [August 18, 2012, 6:27pm UTC](https://discuss.elastic.co/t/status-red/8781/1 "2012-08-18T18:27:42Z")
Hi, I have the following problem. I have 2 nodes and 1 index splited into 30 shards and 1 replica. Currently I have 12mln docs (11GB of data in ES). When I tried to delete documents by query, it never finished and ES started using 100% of processor. I stopped both nodes and run only one of them. Since starting the node it uses about 125% of processor and [http://localhost:2902/\_cluster/health](http://localhost:2902/_cluster/health) returns: { - cluster\_name: "production", - status: "red", - timed\_out: false, - number\_of\_nodes: 1, - number\_of\_data\_nodes: 1, - active\_primary\_shards: 0, - active\_shards: 0, - relocating\_shards: 0, - initializing\_shards: 4, - unassigned\_shards: 56 } It looks like this even whole day and ES restart does not help. Could you help me with that ? I have enabled all logs. There are not any gc logs generated and main log file looks like this: [2012-08-18 20:19:49,111][INFO][node] [es1] {0.19.8}[12199]: initializing ... [2012-08-18 20:19:49,119][INFO][plugins] [es1] loaded [], sites [] [2012-08-18 20:19:55,082][INFO][node] [es1] {0.19.8}[12199]: initialized [2012-08-18 20:19:55,082][INFO][node] [es1] {0.19.8}[12199]: starting ... [2012-08-18 20:19:55,168][INFO][transport] [es1] bound\_address {inet[/0.0.0.0:9300]}, publish\_address {inet[/ 10.29.212.95:9300]} [2012-08-18 20:19:58,208][INFO][cluster.service] [es1] new\_master [es1][aNZR5W2RR1G1Hjlir8pdlw][inet[/10.29.212.95:9300]]{rack\_id=es1\_rack}, reason: zen-disco-join (elected\_as\_master) [2012-08-18 20:19:58,220][INFO][discovery] [es1] production/aNZR5W2RR1G1Hjlir8pdlw [2012-08-18 20:20:01,665][INFO][http] [es1] bound\_address {inet[/0.0.0.0:9200]}, publish\_address {inet[/ 10.29.212.95:9200]} [2012-08-18 20:20:01,665][INFO][node] [es1] {0.19.8}[12199]: started Thank you for help. Best regards. Marcin Dojwa. -- ---
**Author:** ![Marcin\_Dojwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcin_dojwa/32/2307_2.png) [@Marcin\_Dojwa](https://discuss.elastic.co/u/Marcin_Dojwa)\ **Post date:** [August 18, 2012, 6:31pm UTC](https://discuss.elastic.co/t/status-red/8781/2 "2012-08-18T18:31:43Z")
OK, it suddenly finished assigning shards. When I started second node it assigned all shards too. Now it is working fine. It looks like it has a problem when I started both nodes at the same time, it could not assign the shards somehow. So, there is no problem anymore. Sorry 🙂 Best regards. Marcin Dojwa. 2012/8/18 Marcin Dojwa [m.dojwa@livechatinc.com](mailto:m.dojwa@livechatinc.com) > Hi, > > I have the following problem. I have 2 nodes and 1 index splited into 30 > shards and 1 replica. Currently I have 12mln docs (11GB of data in ES). > When I tried to delete documents by query, it never finished and ES started > using 100% of processor. I stopped both nodes and run only one of them. > Since starting the node it uses about 125% of processor and > [http://localhost:2902/\_cluster/health](http://localhost:2902/_cluster/health) returns: > { > > - cluster\_name: "production", > - status: "red", > - timed\_out: false, > - number\_of\_nodes: 1, > - number\_of\_data\_nodes: 1, > - active\_primary\_shards: 0, > - active\_shards: 0, > - relocating\_shards: 0, > - initializing\_shards: 4, > - unassigned\_shards: 56 > > } > > It looks like this even whole day and ES restart does not help. Could you > help me with that ? > > I have enabled all logs. There are not any gc logs generated and main log > file looks like this: > [2012-08-18 20:19:49,111][INFO][node] [es1] > {0.19.8}[12199]: initializing ... > [2012-08-18 20:19:49,119][INFO][plugins] [es1] loaded > , sites > [2012-08-18 20:19:55,082][INFO][node] [es1] > {0.19.8}[12199]: initialized > [2012-08-18 20:19:55,082][INFO][node] [es1] > {0.19.8}[12199]: starting ... > [2012-08-18 20:19:55,168][INFO][transport] [es1] > bound\_address {inet[/0.0.0.0:9300]}, publish\_address {inet[/ > 10.29.212.95:9300]} > [2012-08-18 20:19:58,208][INFO][cluster.service] [es1] > new\_master [es1][aNZR5W2RR1G1Hjlir8pdlw][inet[/10.29.212.95:9300]]{rack\_id=es1\_rack}, > reason: zen-disco-join (elected\_as\_master) > [2012-08-18 20:19:58,220][INFO][discovery] [es1] > production/aNZR5W2RR1G1Hjlir8pdlw > [2012-08-18 20:20:01,665][INFO][http] [es1] > bound\_address {inet[/0.0.0.0:9200]}, publish\_address {inet[/ > 10.29.212.95:9200]} > [2012-08-18 20:20:01,665][INFO][node] [es1] > {0.19.8}[12199]: started > > Thank you for help. > > Best regards. > Marcin Dojwa. -- ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 18, 2012, 6:48pm UTC](https://discuss.elastic.co/t/status-red/8781/3 "2012-08-18T18:48:16Z")
Yes. I think it's a best practice to start new nodes only when the cluster is stable (all shards ok). -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 18 août 2012 à 20:31, Marcin Dojwa [m.dojwa@livechatinc.com](mailto:m.dojwa@livechatinc.com) a écrit : > OK, it suddenly finished assigning shards. When I started second node it assigned all shards too. Now it is working fine. It looks like it has a problem when I started both nodes at the same time, it could not assign the shards somehow. So, there is no problem anymore. Sorry 🙂 > > Best regards. > Marcin Dojwa. > > 2012/8/18 Marcin Dojwa [m.dojwa@livechatinc.com](mailto:m.dojwa@livechatinc.com) > Hi, > > I have the following problem. I have 2 nodes and 1 index splited into 30 shards and 1 replica. Currently I have 12mln docs (11GB of data in ES). When I tried to delete documents by query, it never finished and ES started using 100% of processor. I stopped both nodes and run only one of them. Since starting the node it uses about 125% of processor and [http://localhost:2902/\_cluster/health](http://localhost:2902/_cluster/health) returns: > { > > cluster\_name: "production", > > status: "red", > > timed\_out: false, > > number\_of\_nodes: 1, > > number\_of\_data\_nodes: 1, > > active\_primary\_shards: 0, > > active\_shards: 0, > > relocating\_shards: 0, > > initializing\_shards: 4, > > unassigned\_shards: 56 > > } > > It looks like this even whole day and ES restart does not help. Could you help me with that ? > > I have enabled all logs. There are not any gc logs generated and main log file looks like this: > [2012-08-18 20:19:49,111][INFO][node] [es1] {0.19.8}[12199]: initializing ... > [2012-08-18 20:19:49,119][INFO][plugins] [es1] loaded , sites > [2012-08-18 20:19:55,082][INFO][node] [es1] {0.19.8}[12199]: initialized > [2012-08-18 20:19:55,082][INFO][node] [es1] {0.19.8}[12199]: starting ... > [2012-08-18 20:19:55,168][INFO][transport] [es1] bound\_address {inet[/0.0.0.0:9300]}, publish\_address {inet[/10.29.212.95:9300]} > [2012-08-18 20:19:58,208][INFO][cluster.service] [es1] new\_master [es1][aNZR5W2RR1G1Hjlir8pdlw][inet[/10.29.212.95:9300]]{rack\_id=es1\_rack}, reason: zen-disco-join (elected\_as\_master) > [2012-08-18 20:19:58,220][INFO][discovery] [es1] production/aNZR5W2RR1G1Hjlir8pdlw > [2012-08-18 20:20:01,665][INFO][http] [es1] bound\_address {inet[/0.0.0.0:9200]}, publish\_address {inet[/10.29.212.95:9200]} > [2012-08-18 20:20:01,665][INFO][node] [es1] {0.19.8}[12199]: started > > Thank you for help. > > Best regards. > Marcin Dojwa. > > -- -- ---
**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:15am UTC](https://discuss.elastic.co/t/status-red/8781/4 "2017-07-06T03:15:54Z")
Closed on July 6, 2017, 3:15am UTC