# Nodes aren't joining cluster with ec2 discovery **URL:** \ **Category:** Elasticsearch\ **Created:** [July 24, 2013, 6:12pm UTC](https://discuss.elastic.co/t/nodes-arent-joining-cluster-with-ec2-discovery/12922 "2013-07-24T18:12:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Barry\_Morrison](https://avatars.discourse-cdn.com/v4/letter/b/3bc359/32.png) [@Barry\_Morrison](https://discuss.elastic.co/u/Barry_Morrison)\ **Post date:** [July 24, 2013, 6:12pm UTC](https://discuss.elastic.co/t/nodes-arent-joining-cluster-with-ec2-discovery/12922/1 "2013-07-24T18:12:30Z")
Ubuntu 12.04.2 with ES 0.20.6 elasticsearch.yml: cluster.name: my-search cloud: aws: access\_key: mine secret\_key: mine dicovery: type: ec2 ec2: tag: role: elasticsearch host\_type: private\_ip availability\_zones: us-west-2a, us-west-2b, us-west-2c on any node I can run: curl -XGET '[http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)' and get { "cluster\_name" : "my-search", "status" : "green", "timed\_out" : false, "number\_of\_nodes" : 1, "number\_of\_data\_nodes" : 1, "active\_primary\_shards" : 0, "active\_shards" : 0, "relocating\_shards" : 0, "initializing\_shards" : 0, "unassigned\_shards" : 0 } No nodes every join the cluster. AWS credentials are EC2-Read-only (EC2::Describe). I followed this guide: [http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/) And here is one of the logs: [2013-07-24 18:07:40,078][WARN][common.jna] Unknown mlockall error 0 [2013-07-24 18:07:40,088][INFO][node] [Vanguard] {0.20.6}[13994]: initializing ... [2013-07-24 18:07:40,107][INFO][plugins] [Vanguard] loaded [cloud-aws], sites [] [2013-07-24 18:07:42,029][DEBUG][discovery.zen.ping.multicast] [Vanguard] using group [224.2.2.4], with port [54328], ttl [3], and address [null] [2013-07-24 18:07:42,034][DEBUG][discovery.zen.ping.unicast] [Vanguard] using initial hosts [], with concurrent\_connects [10] [2013-07-24 18:07:42,036][DEBUG][discovery.zen] [Vanguard] using ping.timeout [3s], master\_election.filter\_client [true], master\_election.filter\_data [false] [2013-07-24 18:07:42,037][DEBUG][discovery.zen.elect] [Vanguard] using minimum\_master\_nodes [-1] [2013-07-24 18:07:42,039][DEBUG][discovery.zen.fd] [Vanguard] [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2013-07-24 18:07:42,045][DEBUG][discovery.zen.fd] [Vanguard] [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2013-07-24 18:07:43,192][INFO][node] [Vanguard] {0.20.6}[13994]: initialized [2013-07-24 18:07:43,193][INFO][node] [Vanguard] {0.20.6}[13994]: starting ... [2013-07-24 18:07:43,319][INFO][transport] [Vanguard] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/10.22.132.213:9300]} [2013-07-24 18:07:46,341][DEBUG][discovery.zen] [Vanguard] filtered ping responses: (filter\_client[true], filter\_data[false]) {none} [2013-07-24 18:07:46,345][INFO][cluster.service] [Vanguard] new\_master [Vanguard][2XcG9aHOSsSgsc-tiF6pkA][inet[/10.22.132.213:9300]], reason: zen-disco-join (elected\_as\_master) [2013-07-24 18:07:46,378][INFO][discovery] [Vanguard] my-search/2XcG9aHOSsSgsc-tiF6pkA [2013-07-24 18:07:46,444][INFO][http] [Vanguard] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/10.22.132.213:9200]} [2013-07-24 18:07:46,444][INFO][node] [Vanguard] {0.20.6}[13994]: started [2013-07-24 18:07:46,497][INFO][gateway] [Vanguard] recovered [0] indices into cluster\_state -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Norberto\_Meijome](https://avatars.discourse-cdn.com/v4/letter/n/ed655f/32.png) [@Norberto\_Meijome](https://discuss.elastic.co/u/Norberto_Meijome)\ **Post date:** [July 25, 2013, 5:06am UTC](https://discuss.elastic.co/t/nodes-arent-joining-cluster-with-ec2-discovery/12922/2 "2013-07-25T05:06:13Z")
It looks like you are still using multicast, which won't work at all in AWS. Plugin does work BTW, make sure you are allowing TCP/9300 from the sec group your instances live (i.e., from the secgroup to itself). On 25/07/2013 4:12 AM, "Barry Morrison" [barry@versal.com](mailto:barry@versal.com) wrote: > Ubuntu 12.04.2 with ES 0.20.6 > > elasticsearch.yml: > > cluster.name: my-search > cloud: > aws: > access\_key: mine > secret\_key: mine > > dicovery: > type: ec2 > ec2: > tag: > role: elasticsearch > host\_type: private\_ip > availability\_zones: us-west-2a, us-west-2b, us-west-2c > > on any node I can run: curl -XGET ' > [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)' > > and get > { > "cluster\_name" : "my-search", > "status" : "green", > "timed\_out" : false, > "number\_of\_nodes" : 1, > "number\_of\_data\_nodes" : 1, > "active\_primary\_shards" : 0, > "active\_shards" : 0, > "relocating\_shards" : 0, > "initializing\_shards" : 0, > "unassigned\_shards" : 0 > } > > No nodes every join the cluster. AWS credentials are EC2-Read-only > (EC2::Describe). > > I followed this guide: > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/) > > And here is one of the logs: > > [2013-07-24 18:07:40,078][WARN][common.jna] Unknown > mlockall error 0 > [2013-07-24 18:07:40,088][INFO][node] [Vanguard] > {0.20.6}[13994]: initializing ... > [2013-07-24 18:07:40,107][INFO][plugins] [Vanguard] > loaded [cloud-aws], sites > [2013-07-24 18:07:42,029][DEBUG][discovery.zen.ping.multicast] [Vanguard] > using group [224.2.2.4], with port [54328], ttl [3], and address [null] > [2013-07-24 18:07:42,034][DEBUG][discovery.zen.ping.unicast] [Vanguard] > using initial hosts , with concurrent\_connects [10] > [2013-07-24 18:07:42,036][DEBUG][discovery.zen] [Vanguard] > using ping.timeout [3s], master\_election.filter\_client [true], > master\_election.filter\_data [false] > [2013-07-24 18:07:42,037][DEBUG][discovery.zen.elect] [Vanguard] > using minimum\_master\_nodes [-1] > [2013-07-24 18:07:42,039][DEBUG][discovery.zen.fd] [Vanguard] > [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > [2013-07-24 18:07:42,045][DEBUG][discovery.zen.fd] [Vanguard] > [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > [2013-07-24 18:07:43,192][INFO][node] [Vanguard] > {0.20.6}[13994]: initialized > [2013-07-24 18:07:43,193][INFO][node] [Vanguard] > {0.20.6}[13994]: starting ... > [2013-07-24 18:07:43,319][INFO][transport] [Vanguard] > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > 10.22.132.213:9300]} > [2013-07-24 18:07:46,341][DEBUG][discovery.zen] [Vanguard] > filtered ping responses: (filter\_client[true], filter\_data[false]) {none} > [2013-07-24 18:07:46,345][INFO][cluster.service] [Vanguard] > new\_master [Vanguard][2XcG9aHOSsSgsc-tiF6pkA][inet[/10.22.132.213:9300]], > reason: zen-disco-join (elected\_as\_master) > [2013-07-24 18:07:46,378][INFO][discovery] [Vanguard] > my-search/2XcG9aHOSsSgsc-tiF6pkA > [2013-07-24 18:07:46,444][INFO][http] [Vanguard] > bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/ > 10.22.132.213:9200]} > [2013-07-24 18:07:46,444][INFO][node] [Vanguard] > {0.20.6}[13994]: started > [2013-07-24 18:07:46,497][INFO][gateway] [Vanguard] > recovered [0] indices into cluster\_state > > -- > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Norberto\_Meijome](https://avatars.discourse-cdn.com/v4/letter/n/ed655f/32.png) [@Norberto\_Meijome](https://discuss.elastic.co/u/Norberto_Meijome)\ **Post date:** [July 25, 2013, 5:06am UTC](https://discuss.elastic.co/t/nodes-arent-joining-cluster-with-ec2-discovery/12922/3 "2013-07-25T05:06:44Z")
BTW if u can, upgrade your version of Elasticsearch. On 25/07/2013 4:12 AM, "Barry Morrison" [barry@versal.com](mailto:barry@versal.com) wrote: > Ubuntu 12.04.2 with ES 0.20.6 > > elasticsearch.yml: > > cluster.name: my-search > cloud: > aws: > access\_key: mine > secret\_key: mine > > dicovery: > type: ec2 > ec2: > tag: > role: elasticsearch > host\_type: private\_ip > availability\_zones: us-west-2a, us-west-2b, us-west-2c > > on any node I can run: curl -XGET ' > [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)' > > and get > { > "cluster\_name" : "my-search", > "status" : "green", > "timed\_out" : false, > "number\_of\_nodes" : 1, > "number\_of\_data\_nodes" : 1, > "active\_primary\_shards" : 0, > "active\_shards" : 0, > "relocating\_shards" : 0, > "initializing\_shards" : 0, > "unassigned\_shards" : 0 > } > > No nodes every join the cluster. AWS credentials are EC2-Read-only > (EC2::Describe). > > I followed this guide: > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/) > > And here is one of the logs: > > [2013-07-24 18:07:40,078][WARN][common.jna] Unknown > mlockall error 0 > [2013-07-24 18:07:40,088][INFO][node] [Vanguard] > {0.20.6}[13994]: initializing ... > [2013-07-24 18:07:40,107][INFO][plugins] [Vanguard] > loaded [cloud-aws], sites > [2013-07-24 18:07:42,029][DEBUG][discovery.zen.ping.multicast] [Vanguard] > using group [224.2.2.4], with port [54328], ttl [3], and address [null] > [2013-07-24 18:07:42,034][DEBUG][discovery.zen.ping.unicast] [Vanguard] > using initial hosts , with concurrent\_connects [10] > [2013-07-24 18:07:42,036][DEBUG][discovery.zen] [Vanguard] > using ping.timeout [3s], master\_election.filter\_client [true], > master\_election.filter\_data [false] > [2013-07-24 18:07:42,037][DEBUG][discovery.zen.elect] [Vanguard] > using minimum\_master\_nodes [-1] > [2013-07-24 18:07:42,039][DEBUG][discovery.zen.fd] [Vanguard] > [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > [2013-07-24 18:07:42,045][DEBUG][discovery.zen.fd] [Vanguard] > [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > [2013-07-24 18:07:43,192][INFO][node] [Vanguard] > {0.20.6}[13994]: initialized > [2013-07-24 18:07:43,193][INFO][node] [Vanguard] > {0.20.6}[13994]: starting ... > [2013-07-24 18:07:43,319][INFO][transport] [Vanguard] > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > 10.22.132.213:9300]} > [2013-07-24 18:07:46,341][DEBUG][discovery.zen] [Vanguard] > filtered ping responses: (filter\_client[true], filter\_data[false]) {none} > [2013-07-24 18:07:46,345][INFO][cluster.service] [Vanguard] > new\_master [Vanguard][2XcG9aHOSsSgsc-tiF6pkA][inet[/10.22.132.213:9300]], > reason: zen-disco-join (elected\_as\_master) > [2013-07-24 18:07:46,378][INFO][discovery] [Vanguard] > my-search/2XcG9aHOSsSgsc-tiF6pkA > [2013-07-24 18:07:46,444][INFO][http] [Vanguard] > bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/ > 10.22.132.213:9200]} > [2013-07-24 18:07:46,444][INFO][node] [Vanguard] > {0.20.6}[13994]: started > [2013-07-24 18:07:46,497][INFO][gateway] [Vanguard] > recovered [0] indices into cluster\_state > > -- > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:24am UTC](https://discuss.elastic.co/t/nodes-arent-joining-cluster-with-ec2-discovery/12922/4 "2017-07-06T02:24:39Z")