I have a cluster with 3 nodes, each node has the name set in the elasticsearch.yml
Today I've upgraded to ES 2.1 from 2.0 and found an interesting behaviour .
Whenever I restart a node, it comes back with a totally different ID .
Example :
[2015-11-25 11:37:14,356][INFO][cluster.service][node1] removed {{node2}{m6A6gifIT527eqLasHxP_g}
[2015-11-25 11:37:22,328][INFO][cluster.service][node1] added {{node2}{nsoiqwmVTu6EC-dQnEoLaQ}
If you are using Marvel, you will end up with a stale node, based on the old id .
Did anyone else bumped into this ?
In 2.0, the nodes were coming back with the same id .
the change of the node id is actually expected behaviour after restart. The id will be randomly generated unless you specify a specific seed ("discovery.id.seed") in your settings. Unless you did that in your 2.0 installation, I'm wondering how you would get the same id there.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.