Health Status Red(Accidentally started another node)

Elastic Stack Elasticsearch
1

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1548aca9-50b4-42be-8b08-6be1a4d99bff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

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 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.
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?utm_medium=email&utm_source=footer
.
For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_PrYoYFwysLL5Nr%3Dh4sfT0wRo-y8fcQPiDNNpTpOTLXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/02b1b570-a7e9-42b8-af25-45714612fa6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

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 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.
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?utm_medium=email&utm_source=footer
.
For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-EJs2hvkUoiu4B9STgxuYX8%2BVvYdBJ95VFiTku0WeAEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.