# Health Status Red(Accidentally started another node) **URL:** \ **Category:** Elasticsearch\ **Created:** [April 1, 2015, 12:08am UTC](https://discuss.elastic.co/t/health-status-red-accidentally-started-another-node/23024 "2015-04-01T00:08:53Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ES\_USER362](https://avatars.discourse-cdn.com/v4/letter/e/97f17d/32.png) [@ES\_USER362](https://discuss.elastic.co/u/ES_USER362)\ **Post date:** [April 1, 2015, 12:08am UTC](https://discuss.elastic.co/t/health-status-red-accidentally-started-another-node/23024/1 "2015-04-01T00:08:53Z")
Today, I accidentally started another node on a different machine on the same LAN which resulted in my first ES instance adding this new node to the cluster. I killed this second node with SIGKILL and restarted my original ES instance. However, on checking the health status of the various indices, a lot of them show red. The one's that show a red status have no. of replicas set to 0. The ones that are green had the number of replicas set to 1. Is there any way I can cleanly get the health back to Green without deleting and re-indexing. I am using the default setting of having 5 shards per index. Also, for each index that has its' status as red has exactly one shard that is unassigned. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1548aca9-50b4-42be-8b08-6be1a4d99bff%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1548aca9-50b4-42be-8b08-6be1a4d99bff%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 1, 2015, 1:23am UTC](https://discuss.elastic.co/t/health-status-red-accidentally-started-another-node/23024/2 "2015-04-01T01:23:27Z")
Restart the other node, let it join and then bring the cluster back to green. Then either 1) add replicas so each node has the data and remove the old node and set replicas to 0, or 2) disable allocation and move the shards off the other node to the main one manually. On 1 April 2015 at 11:08, Shomo [shoumitradosco1@gmail.com](mailto:shoumitradosco1@gmail.com) wrote: > Today, I accidentally started another node on a different machine on the > same LAN which resulted in my first ES instance adding this new node to the > cluster. I killed this second node with SIGKILL and restarted my original > ES instance. However, on checking the health status of the various > indices, a lot of them show red. The one's that show a red status have no. > of replicas set to 0. The ones that are green had the number of replicas > set to 1. Is there any way I can cleanly get the health back to Green > without deleting and re-indexing. I am using the default setting of having > 5 shards per index. Also, for each index that has its' status as red has > exactly one shard that is unassigned. > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/1548aca9-50b4-42be-8b08-6be1a4d99bff%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1548aca9-50b4-42be-8b08-6be1a4d99bff%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/1548aca9-50b4-42be-8b08-6be1a4d99bff%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1548aca9-50b4-42be-8b08-6be1a4d99bff%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X\_PrYoYFwysLL5Nr%3Dh4sfT0wRo-y8fcQPiDNNpTpOTLXw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_PrYoYFwysLL5Nr%3Dh4sfT0wRo-y8fcQPiDNNpTpOTLXw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![ES\_USER362](https://avatars.discourse-cdn.com/v4/letter/e/97f17d/32.png) [@ES\_USER362](https://discuss.elastic.co/u/ES_USER362)\ **Post date:** [April 1, 2015, 1:39am UTC](https://discuss.elastic.co/t/health-status-red-accidentally-started-another-node/23024/3 "2015-04-01T01:39:59Z")
Thank you for the solution ! A quick clarification though. So I am assuming that on restarting the second node, the cluster will automatically come back to green, right? Also, is it possible that instead of restarting the second node(which was accidental and not really needed), I can force shard allocation of unassigned shard to my original node? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/02b1b570-a7e9-42b8-af25-45714612fa6f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/02b1b570-a7e9-42b8-af25-45714612fa6f%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 1, 2015, 2:00am UTC](https://discuss.elastic.co/t/health-status-red-accidentally-started-another-node/23024/4 "2015-04-01T02:00:06Z")
It should, only way to know is to try. You can try to force allocation if that node has them there. On 1 April 2015 at 12:39, Shomo [shoumitradosco1@gmail.com](mailto:shoumitradosco1@gmail.com) wrote: > Thank you for the solution ! A quick clarification though. So I am > assuming that on restarting the second node, the cluster will automatically > come back to green, right? Also, is it possible that instead of restarting > the second node(which was accidental and not really needed), I can force > shard allocation of unassigned shard to my original node? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/02b1b570-a7e9-42b8-af25-45714612fa6f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/02b1b570-a7e9-42b8-af25-45714612fa6f%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/02b1b570-a7e9-42b8-af25-45714612fa6f%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/02b1b570-a7e9-42b8-af25-45714612fa6f%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-EJs2hvkUoiu4B9STgxuYX8%2BVvYdBJ95VFiTku0WeAEw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-EJs2hvkUoiu4B9STgxuYX8%2BVvYdBJ95VFiTku0WeAEw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:22am UTC](https://discuss.elastic.co/t/health-status-red-accidentally-started-another-node/23024/5 "2017-07-06T00:22:31Z")