Starting a non elligible-master node first, breaks the cluster creation


(Bastien Chong) #1

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8bb6e4f1-2680-4baf-bc09-c6b53e4bc1e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Bastien Chong) #2

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9c144367-a1b3-46da-aa78-bc9fbc866f5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Bastien Chong) #3

Known issue.

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f438745e-7e63-46d6-bf83-ec759ebcaef8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #4