# Starting a non elligible-master node first, breaks the cluster creation **URL:** \ **Category:** Elasticsearch\ **Created:** [March 18, 2014, 7:58pm UTC](https://discuss.elastic.co/t/starting-a-non-elligible-master-node-first-breaks-the-cluster-creation/16440 "2014-03-18T19:58:39Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Bastien\_Chong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bastien_chong/32/1393_2.png) [@Bastien\_Chong](https://discuss.elastic.co/u/Bastien_Chong)\ **Post date:** [March 18, 2014, 7:58pm UTC](https://discuss.elastic.co/t/starting-a-non-elligible-master-node-first-breaks-the-cluster-creation/16440/1 "2014-03-18T19:58:39Z")
I have ES 0.90.10. On the same server, I have a master/data instance of ES and a second non-master one. ( _node.master: false_ ) When the master instance is started first, and the non-master afterwards, both are in the same configured cluster. Master is automatically binded to 9200/9300 and the non-master 9201/9301. If I start the non-master first, it stops working. (ports are inverted) I tested with both the AWS EC2 plugin discovery and the unicast discovery. That tells me, if the first node to start can't be master, even by starting a second instance that can with the same cluster.name, the cluster can't be created. -- 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/8bb6e4f1-2680-4baf-bc09-c6b53e4bc1e6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8bb6e4f1-2680-4baf-bc09-c6b53e4bc1e6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bastien\_Chong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bastien_chong/32/1393_2.png) [@Bastien\_Chong](https://discuss.elastic.co/u/Bastien_Chong)\ **Post date:** [March 19, 2014, 12:31pm UTC](https://discuss.elastic.co/t/starting-a-non-elligible-master-node-first-breaks-the-cluster-creation/16440/2 "2014-03-19T12:31:11Z")
It looks like a major issue to me, am I doing something wrong ? On Tuesday, March 18, 2014 3:58:39 PM UTC-4, Bastien Chong wrote: > I have ES 0.90.10. > > On the same server, I have a master/data instance of ES and a second > non-master one. ( _node.master: false_ ) > > When the master instance is started first, and the non-master afterwards, > both are in the same configured cluster. > Master is automatically binded to 9200/9300 and the non-master 9201/9301. > > If I start the non-master first, it stops working. (ports are inverted) > > I tested with both the AWS EC2 plugin discovery and the unicast discovery. > > That tells me, if the first node to start can't be master, even by > starting a second instance that can with the same cluster.name, the > cluster can't be created. -- 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/9c144367-a1b3-46da-aa78-bc9fbc866f5e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9c144367-a1b3-46da-aa78-bc9fbc866f5e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bastien\_Chong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bastien_chong/32/1393_2.png) [@Bastien\_Chong](https://discuss.elastic.co/u/Bastien_Chong)\ **Post date:** [March 19, 2014, 12:44pm UTC](https://discuss.elastic.co/t/starting-a-non-elligible-master-node-first-breaks-the-cluster-creation/16440/3 "2014-03-19T12:44:44Z")
Known issue. > > > Hello, > > I have ES 0.90.10, I couldn't test with the latest release, I honestly d…on't know if maybe it was fixed since. > > On the same server, I have a master/data instance of ES and a second non-master. ( node.master: false ) > > When the master instance is started first, and the non-master afterwards, both are in the same configured cluster. > > If I start the non-master first, it stops working. > > I also tested with both the AWS EC2 plugin discovery and the unicast discovery. > > That tells me, if the first node to start can't be master, even by starting a second instance that can, with the same cluster.name, the cluster can't be created. On Wednesday, March 19, 2014 8:31:11 AM UTC-4, Bastien Chong wrote: > It looks like a major issue to me, am I doing something wrong ? > > On Tuesday, March 18, 2014 3:58:39 PM UTC-4, Bastien Chong wrote: > > > I have ES 0.90.10. > > > > On the same server, I have a master/data instance of ES and a second > > non-master one. ( _node.master: false_ ) > > > > When the master instance is started first, and the non-master afterwards, > > both are in the same configured cluster. > > Master is automatically binded to 9200/9300 and the non-master 9201/9301. > > > > If I start the non-master first, it stops working. (ports are inverted) > > > > I tested with both the AWS EC2 plugin discovery and the unicast discovery. > > > > That tells me, if the first node to start can't be master, even by > > starting a second instance that can with the same cluster.name, the > > cluster can't be created. -- 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/f438745e-7e63-46d6-bf83-ec759ebcaef8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f438745e-7e63-46d6-bf83-ec759ebcaef8%40googlegroups.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, 1:42am UTC](https://discuss.elastic.co/t/starting-a-non-elligible-master-node-first-breaks-the-cluster-creation/16440/4 "2017-07-06T01:42:12Z")
Closed on July 6, 2017, 1:42am UTC