It was immediate on my laptop.
--
David Pilato | Technical Advocate | elasticsearch.com
david.pilato@elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs
Le 18 septembre 2014 à 17:32:18, Jinyuan Zhou (zhou.jinyuan@gmail.com) a écrit:
David,
Thanks for taking time to look at my issue. My issue is probably too slow to find a master node to join. I was wondering if non master eligible nodes takes longer to find a master node. May be some time out happened. I was looking for some parameters to allow more time to find a master node. I played with discovery.zen.fd.ping_timeout. I set it 90 seconds (default is 30s). It didn't make a difference. The message still says "waited for 30s and no initial state was set by the discovery".
Regards,
Jack
Jinyuan (Jack) Zhou
On Wed, Sep 17, 2014 at 11:39 PM, David Pilato david@pilato.fr wrote:
Ok. I tried to reproduce it on elasticsearch 1.3.2.
First node started:
bin/elasticsearch -Ddiscovery.zen.ping.multicast.enabled=false -Des.discovery.zen.ping.unicast.hosts=localhost
[2014-09-18 08:36:05,417][INFO ][cluster.service ] [Crusader] new_master [Crusader][i3SU0cwSQeizbN_MUqAXSw][MacBook-Air-de-David.local][inet[/192.168.0.15:9300]], reason: zen-disco-join (elected_as_master)
Second node (client):
bin/elasticsearch -Ddiscovery.zen.ping.multicast.enabled=false -Des.discovery.zen.ping.unicast.hosts=localhost -Des.node.data=false -Des.node.master=false
[2014-09-18 08:36:36,444][INFO ][cluster.service ] [Sekhmet] detected_master [Crusader][i3SU0cwSQeizbN_MUqAXSw][MacBook-Air-de-David.local][inet[/192.168.0.15:9300]], added {[Crusader][i3SU0cwSQeizbN_MUqAXSw][MacBook-Air-de-David.local][inet[/192.168.0.15:9300]],}, reason: zen-disco-receive(from master [[Crusader][i3SU0cwSQeizbN_MUqAXSw][MacBook-Air-de-David.local][inet[/192.168.0.15:9300]]])
So to me everything is working fine.
I don't understand what you are exactly doing. May be you should try to change logging.yml to DEBUG or TRACE and see what's going on in your client node.
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 18 septembre 2014 à 02:54:31, Jinyuan Zhou (zhou.jinyuan@gmail.com) a écrit:
yes.
Jinyuan (Jack) Zhou
On Wed, Sep 17, 2014 at 5:52 PM, David Pilato david@pilato.fr wrote:
And when you remove -Des.node.master=false the client node is able to join the cluster?
I mean "join" the cluster so you can see it joining in the master node logs.
--
David 
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 17 sept. 2014 à 22:31, Jinyuan Zhou zhou.jinyuan@gmail.com a écrit :
Yes.
The settings are almost same for all nodes
discovery.zen.ping.multicast.enabled: false # this is in elasticsearch.yml
-Des.discovery.zen.ping.unicast.hosts= this is java -D parameter
Jinyuan (Jack) Zhou
On Wed, Sep 17, 2014 at 1:27 PM, David Pilato david@pilato.fr wrote:
When you start the client node, did you set list of master nodes as unicast hosts?
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 17 sept. 2014 à 22:13, Jinyuan Zhou zhou.jinyuan@gmail.com a écrit :
I am using unicast with out of box zen discovery.
discovery.zen.ping.multicast.enabled: false
-Des.discovery.zen.ping.unicast.hosts=
Jinyuan (Jack) Zhou
On Wed, Sep 17, 2014 at 1:08 PM, David Pilato david@pilato.fr wrote:
Are you using multicast or unicast or a plugin for discovery?
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 17 sept. 2014 à 21:49, Jinyuan Zhou zhou.jinyuan@gmail.com a écrit :
yes. cluster name is set to be the same on all 12 nodes
Jinyuan (Jack) Zhou
On Wed, Sep 17, 2014 at 12:24 PM, David Pilato david@pilato.fr wrote:
Did you set the same cluster name?
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 17 sept. 2014 à 21:09, Jinyuan Zhou zhou.jinyuan@gmail.com a écrit :
Sorry I didn't explain clearly. I have a cluster with 12 nodes. 10 are master eligible. 2 are client only (es.node.data=false, es.node.master=false). I have configured the minimal number of nodes to form a cluster is 6. all the boxes hosting 12 es instances are on the same rack. The problem is that these two client-only nodes cannot join the cluster. It cannot discovers the master. But if I make them master eligible it discover the master node immediately.
I don't understand what make the differences.
Thanks,
Jack
Jinyuan (Jack) Zhou
On Wed, Sep 17, 2014 at 11:54 AM, David Pilato david@pilato.fr wrote:
A cluster needs a master node.
You need at least one node which could be elected as master.
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 17 sept. 2014 à 20:08, Jinyuan Zhou zhou.jinyuan@gmail.com a écrit :
I have two nodes with this configuration -Des.node.data=false -Des.node.master=false when I start. But these nodes have experiencing finding master node. Here is message.
[2014-09-17 16:51:10,457][WARN ][discovery ] [mynodename] waited for 30s and no initial state was set by the discovery
However, If I remove -Des.node.master=false.
The discovery have no issue.
Thanks,
Jack
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/xMobdE6tsCA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/348CFDC1-FF38-4D05-9453-74CEFAF53309%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/xMobdE6tsCA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/24C43DE6-E733-4EE0-9959-3544CA47EE40%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/xMobdE6tsCA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2E9694D7-374B-4C9E-98E1-8808F5518373%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/xMobdE6tsCA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/51A25E3E-D8E6-4C13-A622-87165D7FEB52%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/xMobdE6tsCA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/C0EE7E0F-E825-4100-8AFD-05013321AE61%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/xMobdE6tsCA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/etPan.541a7e19.613efdc5.3c6%40MacBook-Air-de-David.local.
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/CANBTPCHU4bYdbx%2BSYCatpM7jScnbketzhp%3D5PBjwD6R6AKRUDQ%40mail.gmail.com.
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/etPan.541bcb2c.46e87ccd.18d1%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.
