OK, it also happens to some degree with 1.4.0-beta, although overall it’s much better on beta. I wasn’t able to get my 12 node cluster up on 1.4.0 after several hours of fiddling, but 1.4.0-beta did come up.
From: elasticsearch@googlegroups.com [mailto:elasticsearch@googlegroups.com] On Behalf Of Janet Sullivan Sent: Saturday, November 08, 2014 9:26 PM To: elasticsearch@googlegroups.com Subject: RE: Nodes not joining after 1.4.0 upgrade But it DOES happen with 1.3.5. Hmmm…. From: elasticsearch@googlegroups.com<mailto:elasticsearch@googlegroups.com> [mailto:elasticsearch@googlegroups.com] On Behalf Of Janet Sullivan Sent: Saturday, November 08, 2014 9:24 PM To: elasticsearch@googlegroups.com<mailto:elasticsearch@googlegroups.com> Subject: RE: Nodes not joining after 1.4.0 upgrade Note: This issue doesn’t happen with 1.4.0-beta1 From: elasticsearch@googlegroups.com<mailto:elasticsearch@googlegroups.com> [mailto:elasticsearch@googlegroups.com] On Behalf Of Janet Sullivan Sent: Saturday, November 08, 2014 8:46 PM To: elasticsearch@googlegroups.com<mailto:elasticsearch@googlegroups.com> Subject: Nodes not joining after 1.4.0 upgrade I’ve upgraded a couple of clusters to 1.4.0 from 1.3.4. On both of them, I had nodes that spewed the following, and were slow to join, if they joined at all: [2014-11-09 04:33:45,995][INFO ][discovery.zen ] [gnslogstash3] failed to send join request to master [[gnslogstash10][9nx_f_NiQtCntgnD2q7k0g][gnslogstash10][inet[/10.0.0.29:9300]]{data=false, master=true}], reason [ElasticsearchTimeoutException[Timeout waiting for task.]] [2014-11-09 04:34:49,776][INFO ][discovery.zen ] [gnslogstash3] failed to send join request to master [[gnslogstash10][9nx_f_NiQtCntgnD2q7k0g][gnslogstash10][inet[/10.0.0.29:9300]]{data=false, master=true}], reason [ElasticsearchTimeoutException[Timeout waiting for task.]] [2014-11-09 04:35:53,571][INFO ][discovery.zen ] [gnslogstash3] failed to send join request to master [[gnslogstash10][9nx_f_NiQtCntgnD2q7k0g][gnslogstash10][inet[/10.0.0.29:9300]]{data=false, master=true}], reason [ElasticsearchTimeoutException[Timeout waiting for task.]] [2014-11-09 04:36:57,353][INFO ][discovery.zen ] [gnslogstash3] failed to send join request to master [[gnslogstash10][9nx_f_NiQtCntgnD2q7k0g][gnslogstash10][inet[/10.0.0.29:9300]]{data=false, master=true}], reason [ElasticsearchTimeoutException[Timeout waiting for task.]] [2014-11-09 04:38:01,120][INFO ][discovery.zen ] [gnslogstash3] failed to send join request to master [[gnslogstash10][9nx_f_NiQtCntgnD2q7k0g][gnslogstash10][inet[/10.0.0.29:9300]]{data=false, master=true}], reason [ElasticsearchTimeoutException[Timeout waiting for task.]] [2014-11-09 04:39:04,885][INFO ][discovery.zen ] [gnslogstash3] failed to send join request to master [[gnslogstash10][9nx_f_NiQtCntgnD2q7k0g][gnslogstash10][inet[/10.0.0.29:9300]]{data=false, master=true}], reason [ElasticsearchTimeoutException[Timeout waiting for task.]] [2014-11-09 04:40:08,657][INFO ][discovery.zen ] [gnslogstash3] failed to send join request to master [[gnslogstash10][9nx_f_NiQtCntgnD2q7k0g][gnslogstash10][inet[/10.0.0.29:9300]]{data=false, master=true}], reason [ElasticsearchTimeoutException[Timeout waiting for task.]] I’m able to telnet to port 9300 on gnslogstash10 in this example from gnslogstash3 with no issue, but this cluster doesn’t want to bring all its nodes up. The more nodes added, the more likely a join will fail. In this example, 9 nodes are up, but 3 nodes don’t want to join. ☹ Thoughts? -- 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+unsubscr...@googlegroups.com<mailto:elasticsearch+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2817051de55a4f96a4bd173f26177f29%40CY1PR0701MB1164.namprd07.prod.outlook.com<https://groups.google.com/d/msgid/elasticsearch/2817051de55a4f96a4bd173f26177f29%40CY1PR0701MB1164.namprd07.prod.outlook.com?utm_medium=email&utm_source=footer>. 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+unsubscr...@googlegroups.com<mailto:elasticsearch+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2098c745e47648d6b668b8c699f8750c%40CY1PR0701MB1164.namprd07.prod.outlook.com<https://groups.google.com/d/msgid/elasticsearch/2098c745e47648d6b668b8c699f8750c%40CY1PR0701MB1164.namprd07.prod.outlook.com?utm_medium=email&utm_source=footer>. 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+unsubscr...@googlegroups.com<mailto:elasticsearch+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/47110bba4ae6400c9888beb70972c6f0%40CY1PR0701MB1164.namprd07.prod.outlook.com<https://groups.google.com/d/msgid/elasticsearch/47110bba4ae6400c9888beb70972c6f0%40CY1PR0701MB1164.namprd07.prod.outlook.com?utm_medium=email&utm_source=footer>. 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2a296bdb68984733af72024cfe8657f6%40CY1PR0701MB1164.namprd07.prod.outlook.com. For more options, visit https://groups.google.com/d/optout.
