Re: Health Status Red(Accidentally started another node)

2015-03-31 Thread Shomo
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

Re: Health Status Red(Accidentally started another node)

2015-03-31 Thread Mark Walkom
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,

Re: Health Status Red(Accidentally started another node)

2015-03-31 Thread Mark Walkom
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 shoumitrados...@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

Health Status Red(Accidentally started another node)

2015-03-31 Thread Shomo
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