# AWS nodes don't discover each other **URL:** \ **Category:** Elasticsearch\ **Created:** [October 30, 2013, 8:13pm UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177 "2013-10-30T20:13:35Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![gzion7](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@gzion7](https://discuss.elastic.co/u/gzion7)\ **Post date:** [October 30, 2013, 8:13pm UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/1 "2013-10-30T20:13:35Z")
I have two ES servers in AWS, I have security groups set to allow all traffic from these 2 IPs. I installed the aws plugin. The only changes I've made in the yml file are the cluster name, http.max.content.length, and path to store data. Both nodes start perfectly fine, there are no errors but they don't discover each other. Here are the logs from starting ES on one of the nodes: [2013-10-30 16:11:12,702][INFO][node] [Burstarr] version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12:50:20Z] [2013-10-30 16:11:12,703][INFO][node] [Burstarr] initializing ... [2013-10-30 16:11:12,723][INFO][plugins] [Burstarr] loaded [cloud-aws], sites [] [2013-10-30 16:11:15,199][DEBUG][discovery.zen.ping.unicast] [Burstarr] using initial hosts [], with concurrent\_connects [10] [2013-10-30 16:11:15,202][DEBUG][discovery.zen] [Burstarr] using ping.timeout [3s], master\_election.filter\_client [true], master\_election.filter\_data [false] [2013-10-30 16:11:15,203][DEBUG][discovery.zen.elect] [Burstarr] using minimum\_master\_nodes [-1] [2013-10-30 16:11:15,205][DEBUG][discovery.zen.fd] [Burstarr] [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2013-10-30 16:11:15,211][DEBUG][discovery.zen.fd] [Burstarr] [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2013-10-30 16:11:16,344][DEBUG][gateway.local] [Burstarr] using initial\_shards [quorum], list\_timeout [30s] [2013-10-30 16:11:16,533][DEBUG][indices.recovery] [Burstarr] using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], file\_chunk\_size [512kb], translog\_size [512kb], translog\_ops [1000], and compress [true] [2013-10-30 16:11:16,667][DEBUG][gateway.local.state.meta] [Burstarr] using gateway.local.auto\_import\_dangled [YES], with gateway.local.dangling\_timeout [2h] [2013-10-30 16:11:16,692][DEBUG][gateway.local.state.meta] [Burstarr] took 25ms to load state [2013-10-30 16:11:16,692][DEBUG][gateway.local.state.shards] [Burstarr] took 0s to load started shards state [2013-10-30 16:11:16,746][INFO][node] [Burstarr] initialized [2013-10-30 16:11:16,747][INFO][node] [Burstarr] starting ... [2013-10-30 16:11:16,882][INFO][transport] [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/10.20.4.158:9300]} [2013-10-30 16:11:16,899][TRACE][discovery] [Burstarr] waiting for 30s for the initial state to be set by the discovery [2013-10-30 16:11:19,905][TRACE][discovery.zen] [Burstarr] full ping responses: {none} [2013-10-30 16:11:19,905][DEBUG][discovery.zen] [Burstarr] filtered ping responses: (filter\_client[true], filter\_data[false]) {none} [2013-10-30 16:11:19,912][INFO][cluster.service] [Burstarr] new\_master [Burstarr][pRsc595IQfyXn24N27tbZw][inet[/10.20.4.158:9300]], reason: zen-disco-join (elected\_as\_master) [2013-10-30 16:11:19,977][TRACE][discovery] [Burstarr] initial state set from discovery [2013-10-30 16:11:19,977][INFO][discovery] [Burstarr] elasticsearch/pRsc595IQfyXn24N27tbZw [2013-10-30 16:11:20,012][INFO][http] [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/10.20.4.158:9200]} [2013-10-30 16:11:20,012][INFO][node] [Burstarr] started [2013-10-30 16:11:20,025][INFO][gateway] [Burstarr] 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:** [October 31, 2013, 1:42am UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/2 "2013-10-31T01:42:23Z")
It seems you didn't set discovery type ec2. And obviously u need to provide API keys... And you should also tell it which filter to use ( ie by tag or security group..otherwise it will attempt to connect to any of your hosts...which may be many) On 31/10/2013 7:13 AM, "Gabriel Holder" [gavysdomain@gmail.com](mailto:gavysdomain@gmail.com) wrote: > I have two ES servers in AWS, I have security groups set to allow all > traffic from these 2 IPs. > > I installed the aws plugin. > The only changes I've made in the yml file are the cluster name, > http.max.content.length, and path to store data. > Both nodes start perfectly fine, there are no errors but they don't > discover each other. > > Here are the logs from starting ES on one of the nodes: > [2013-10-30 16:11:12,702][INFO][node] [Burstarr] > version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12:50:20Z] > [2013-10-30 16:11:12,703][INFO][node] [Burstarr] > initializing ... > [2013-10-30 16:11:12,723][INFO][plugins] [Burstarr] > loaded [cloud-aws], sites > [2013-10-30 16:11:15,199][DEBUG][discovery.zen.ping.unicast] [Burstarr] > using initial hosts , with concurrent\_connects [10] > [2013-10-30 16:11:15,202][DEBUG][discovery.zen] [Burstarr] > using ping.timeout [3s], master\_election.filter\_client [true], > master\_election.filter\_data [false] > [2013-10-30 16:11:15,203][DEBUG][discovery.zen.elect] [Burstarr] > using minimum\_master\_nodes [-1] > [2013-10-30 16:11:15,205][DEBUG][discovery.zen.fd] [Burstarr] > [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > [2013-10-30 16:11:15,211][DEBUG][discovery.zen.fd] [Burstarr] > [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > [2013-10-30 16:11:16,344][DEBUG][gateway.local] [Burstarr] > using initial\_shards [quorum], list\_timeout [30s] > [2013-10-30 16:11:16,533][DEBUG][indices.recovery] [Burstarr] > using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], file\_chunk\_size > [512kb], translog\_size [512kb], translog\_ops [1000], and compress [true] > [2013-10-30 16:11:16,667][DEBUG][gateway.local.state.meta] [Burstarr] > using gateway.local.auto\_import\_dangled [YES], with > gateway.local.dangling\_timeout [2h] > [2013-10-30 16:11:16,692][DEBUG][gateway.local.state.meta] [Burstarr] > took 25ms to load state > [2013-10-30 16:11:16,692][DEBUG][gateway.local.state.shards] [Burstarr] > took 0s to load started shards state > [2013-10-30 16:11:16,746][INFO][node] [Burstarr] > initialized > [2013-10-30 16:11:16,747][INFO][node] [Burstarr] > starting ... > [2013-10-30 16:11:16,882][INFO][transport] [Burstarr] > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > 10.20.4.158:9300]} > [2013-10-30 16:11:16,899][TRACE][discovery] [Burstarr] > waiting for 30s for the initial state to be set by the discovery > [2013-10-30 16:11:19,905][TRACE][discovery.zen] [Burstarr] > full ping responses: {none} > [2013-10-30 16:11:19,905][DEBUG][discovery.zen] [Burstarr] > filtered ping responses: (filter\_client[true], filter\_data[false]) {none} > [2013-10-30 16:11:19,912][INFO][cluster.service] [Burstarr] > new\_master [Burstarr][pRsc595IQfyXn24N27tbZw][inet[/10.20.4.158:9300]], > reason: zen-disco-join (elected\_as\_master) > [2013-10-30 16:11:19,977][TRACE][discovery] [Burstarr] > initial state set from discovery > [2013-10-30 16:11:19,977][INFO][discovery] [Burstarr] > elasticsearch/pRsc595IQfyXn24N27tbZw > [2013-10-30 16:11:20,012][INFO][http] [Burstarr] > bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/ > 10.20.4.158:9200]} > [2013-10-30 16:11:20,012][INFO][node] [Burstarr] > started > [2013-10-30 16:11:20,025][INFO][gateway] [Burstarr] > 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:** ![gzion7](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@gzion7](https://discuss.elastic.co/u/gzion7)\ **Post date:** [October 31, 2013, 1:51am UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/3 "2013-10-31T01:51:12Z")
You mean on the bottom of the file where I add my keys? I added those already How can I tag by security groups? On Wednesday, October 30, 2013 9:42:23 PM UTC-4, Norberto Meijome wrote: > It seems you didn't set discovery type ec2. And obviously u need to > provide API keys... > And you should also tell it which filter to use ( ie by tag or security > group..otherwise it will attempt to connect to any of your hosts...which > may be many) > On 31/10/2013 7:13 AM, "Gabriel Holder" \<[gavys...@gmail.com](mailto:gavys...@gmail.com) \\> > wrote: > > > I have two ES servers in AWS, I have security groups set to allow all > > traffic from these 2 IPs. > > > > I installed the aws plugin. > > The only changes I've made in the yml file are the cluster name, > > http.max.content.length, and path to store data. > > Both nodes start perfectly fine, there are no errors but they don't > > discover each other. > > > > Here are the logs from starting ES on one of the nodes: > > [2013-10-30 16:11:12,702][INFO][node] [Burstarr] > > version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12:50:20Z] > > [2013-10-30 16:11:12,703][INFO][node] [Burstarr] > > initializing ... > > [2013-10-30 16:11:12,723][INFO][plugins] [Burstarr] > > loaded [cloud-aws], sites > > [2013-10-30 16:11:15,199][DEBUG][discovery.zen.ping.unicast] [Burstarr] > > using initial hosts , with concurrent\_connects [10] > > [2013-10-30 16:11:15,202][DEBUG][discovery.zen] [Burstarr] > > using ping.timeout [3s], master\_election.filter\_client [true], > > master\_election.filter\_data [false] > > [2013-10-30 16:11:15,203][DEBUG][discovery.zen.elect] [Burstarr] > > using minimum\_master\_nodes [-1] > > [2013-10-30 16:11:15,205][DEBUG][discovery.zen.fd] [Burstarr] > > [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > > [2013-10-30 16:11:15,211][DEBUG][discovery.zen.fd] [Burstarr] > > [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > > [2013-10-30 16:11:16,344][DEBUG][gateway.local] [Burstarr] > > using initial\_shards [quorum], list\_timeout [30s] > > [2013-10-30 16:11:16,533][DEBUG][indices.recovery] [Burstarr] > > using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], file\_chunk\_size > > [512kb], translog\_size [512kb], translog\_ops [1000], and compress [true] > > [2013-10-30 16:11:16,667][DEBUG][gateway.local.state.meta] [Burstarr] > > using gateway.local.auto\_import\_dangled [YES], with > > gateway.local.dangling\_timeout [2h] > > [2013-10-30 16:11:16,692][DEBUG][gateway.local.state.meta] [Burstarr] > > took 25ms to load state > > [2013-10-30 16:11:16,692][DEBUG][gateway.local.state.shards] [Burstarr] > > took 0s to load started shards state > > [2013-10-30 16:11:16,746][INFO][node] [Burstarr] > > initialized > > [2013-10-30 16:11:16,747][INFO][node] [Burstarr] > > starting ... > > [2013-10-30 16:11:16,882][INFO][transport] [Burstarr] > > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > > 10.20.4.158:9300]} > > [2013-10-30 16:11:16,899][TRACE][discovery] [Burstarr] > > waiting for 30s for the initial state to be set by the discovery > > [2013-10-30 16:11:19,905][TRACE][discovery.zen] [Burstarr] > > full ping responses: {none} > > [2013-10-30 16:11:19,905][DEBUG][discovery.zen] [Burstarr] > > filtered ping responses: (filter\_client[true], filter\_data[false]) {none} > > [2013-10-30 16:11:19,912][INFO][cluster.service] [Burstarr] > > new\_master [Burstarr][pRsc595IQfyXn24N27tbZw][inet[/10.20.4.158:9300]], > > reason: zen-disco-join (elected\_as\_master) > > [2013-10-30 16:11:19,977][TRACE][discovery] [Burstarr] > > initial state set from discovery > > [2013-10-30 16:11:19,977][INFO][discovery] [Burstarr] > > elasticsearch/pRsc595IQfyXn24N27tbZw > > [2013-10-30 16:11:20,012][INFO][http] [Burstarr] > > bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/ > > 10.20.4.158:9200]} > > [2013-10-30 16:11:20,012][INFO][node] [Burstarr] > > started > > [2013-10-30 16:11:20,025][INFO][gateway] [Burstarr] > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@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:** [October 31, 2013, 7:36am UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/4 "2013-10-31T07:36:56Z")
It's all in the docs for the ec2 plugin. On 31/10/2013 12:51 PM, "Gabriel Holder" [gavysdomain@gmail.com](mailto:gavysdomain@gmail.com) wrote: > You mean on the bottom of the file where I add my keys? I added those > already > How can I tag by security groups? > > On Wednesday, October 30, 2013 9:42:23 PM UTC-4, Norberto Meijome wrote: > > > It seems you didn't set discovery type ec2. And obviously u need to > > provide API keys... > > And you should also tell it which filter to use ( ie by tag or security > > group..otherwise it will attempt to connect to any of your hosts...which > > may be many) > > On 31/10/2013 7:13 AM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > I have two ES servers in AWS, I have security groups set to allow all > > > traffic from these 2 IPs. > > > > > > I installed the aws plugin. > > > The only changes I've made in the yml file are the cluster name, > > > http.max.content.length, and path to store data. > > > Both nodes start perfectly fine, there are no errors but they don't > > > discover each other. > > > > > > Here are the logs from starting ES on one of the nodes: > > > [2013-10-30 16:11:12,702][INFO][node] [Burstarr] > > > version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12:\*\*50:20Z] > > > [2013-10-30 16:11:12,703][INFO][node] [Burstarr] > > > initializing ... > > > [2013-10-30 16:11:12,723][INFO][plugins] [Burstarr] > > > loaded [cloud-aws], sites > > > [2013-10-30 16:11:15,199][DEBUG][\*\*discovery.zen.ping.unicast] > > > [Burstarr] using initial hosts , with concurrent\_connects [10] > > > [2013-10-30 16:11:15,202][DEBUG][\*\*discovery.zen] > > > [Burstarr] using ping.timeout [3s], master\_election.filter\_client [true], > > > master\_election.filter\_data [false] > > > [2013-10-30 16:11:15,203][DEBUG][\*\*discovery.zen.elect] > > > [Burstarr] using minimum\_master\_nodes [-1] > > > [2013-10-30 16:11:15,205][DEBUG][\*\*discovery.zen.fd] > > > [Burstarr] [master] uses ping\_interval [1s], ping\_timeout [30s], > > > ping\_retries [3] > > > [2013-10-30 16:11:15,211][DEBUG][\*\*discovery.zen.fd] > > > [Burstarr] [node] uses ping\_interval [1s], ping\_timeout [30s], > > > ping\_retries [3] > > > [2013-10-30 16:11:16,344][DEBUG][gateway.\*\*local] > > > [Burstarr] using initial\_shards [quorum], list\_timeout [30s] > > > [2013-10-30 16:11:16,533][DEBUG][indices.\*\*recovery] > > > [Burstarr] using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], > > > file\_chunk\_size [512kb], translog\_size [512kb], translog\_ops [1000], and > > > compress [true] > > > [2013-10-30 16:11:16,667][DEBUG][gateway.\*\*local.state.meta] > > > [Burstarr] using gateway.local.auto\_import\_\*\*dangled [YES], with > > > gateway.local.dangling\_timeout [2h] > > > [2013-10-30 16:11:16,692][DEBUG][gateway.\*\*local.state.meta] > > > [Burstarr] took 25ms to load state > > > [2013-10-30 16:11:16,692][DEBUG][gateway.\*\*local.state.shards] > > > [Burstarr] took 0s to load started shards state > > > [2013-10-30 16:11:16,746][INFO][node] [Burstarr] > > > initialized > > > [2013-10-30 16:11:16,747][INFO][node] [Burstarr] > > > starting ... > > > [2013-10-30 16:11:16,882][INFO][transport] [Burstarr] > > > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > > > 10.20.4.158:9300]} > > > [2013-10-30 16:11:16,899][TRACE][\*\*discovery] > > > [Burstarr] waiting for 30s for the initial state to be set by the discovery > > > [2013-10-30 16:11:19,905][TRACE][\*\*discovery.zen] > > > [Burstarr] full ping responses: {none} > > > [2013-10-30 16:11:19,905][DEBUG][\*\*discovery.zen] > > > [Burstarr] filtered ping responses: (filter\_client[true], > > > filter\_data[false]) {none} > > > [2013-10-30 16:11:19,912][INFO][cluster.service] [Burstarr] > > > new\_master [Burstarr][\*\*pRsc595IQfyXn24N27tbZw][inet[/\*\*10.20.4.158:9300]], > > > reason: zen-disco-join (elected\_as\_master) > > > [2013-10-30 16:11:19,977][TRACE][\*\*discovery] > > > [Burstarr] initial state set from discovery > > > [2013-10-30 16:11:19,977][INFO][discovery] [Burstarr] > > > elasticsearch/\*\*pRsc595IQfyXn24N27tbZw > > > [2013-10-30 16:11:20,012][INFO][http] [Burstarr] > > > bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/ > > > 10.20.4.158:9200]} > > > [2013-10-30 16:11:20,012][INFO][node] [Burstarr] > > > started > > > [2013-10-30 16:11:20,025][INFO][gateway] [Burstarr] > > > 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 elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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). -- 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:** ![gzion7](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@gzion7](https://discuss.elastic.co/u/gzion7)\ **Post date:** [October 31, 2013, 2:54pm UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/5 "2013-10-31T14:54:34Z")
This is what I've added: cloud: aws: access\_key: secret\_key: ``` discovery: type: ec2 groups: SECURITY-GROUP ``` Unfortunately, they still don't see each other On Thursday, October 31, 2013 3:36:56 AM UTC-4, Norberto Meijome wrote: > It's all in the docs for the ec2 plugin. > On 31/10/2013 12:51 PM, "Gabriel Holder" \<[gavys...@gmail.com](mailto:gavys...@gmail.com) \\> > wrote: > > > You mean on the bottom of the file where I add my keys? I added those > > already > > How can I tag by security groups? > > > > On Wednesday, October 30, 2013 9:42:23 PM UTC-4, Norberto Meijome wrote: > > > > > It seems you didn't set discovery type ec2. And obviously u need to > > > provide API keys... > > > And you should also tell it which filter to use ( ie by tag or security > > > group..otherwise it will attempt to connect to any of your hosts...which > > > may be many) > > > On 31/10/2013 7:13 AM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > I have two ES servers in AWS, I have security groups set to allow all > > > > traffic from these 2 IPs. > > > > > > > > I installed the aws plugin. > > > > The only changes I've made in the yml file are the cluster name, > > > > http.max.content.length, and path to store data. > > > > Both nodes start perfectly fine, there are no errors but they don't > > > > discover each other. > > > > > > > > Here are the logs from starting ES on one of the nodes: > > > > [2013-10-30 16:11:12,702][INFO][node] [Burstarr] > > > > version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12:\*\*50:20Z] > > > > [2013-10-30 16:11:12,703][INFO][node] [Burstarr] > > > > initializing ... > > > > [2013-10-30 16:11:12,723][INFO][plugins] [Burstarr] > > > > loaded [cloud-aws], sites > > > > [2013-10-30 16:11:15,199][DEBUG][\*\*discovery.zen.ping.unicast] > > > > [Burstarr] using initial hosts , with concurrent\_connects [10] > > > > [2013-10-30 16:11:15,202][DEBUG][\*\*discovery.zen] > > > > [Burstarr] using ping.timeout [3s], master\_election.filter\_client [true], > > > > master\_election.filter\_data [false] > > > > [2013-10-30 16:11:15,203][DEBUG][\*\*discovery.zen.elect] > > > > [Burstarr] using minimum\_master\_nodes [-1] > > > > [2013-10-30 16:11:15,205][DEBUG][\*\*discovery.zen.fd] > > > > [Burstarr] [master] uses ping\_interval [1s], ping\_timeout [30s], > > > > ping\_retries [3] > > > > [2013-10-30 16:11:15,211][DEBUG][\*\*discovery.zen.fd] > > > > [Burstarr] [node] uses ping\_interval [1s], ping\_timeout [30s], > > > > ping\_retries [3] > > > > [2013-10-30 16:11:16,344][DEBUG][gateway.\*\*local] > > > > [Burstarr] using initial\_shards [quorum], list\_timeout [30s] > > > > [2013-10-30 16:11:16,533][DEBUG][indices.\*\*recovery] > > > > [Burstarr] using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], > > > > file\_chunk\_size [512kb], translog\_size [512kb], translog\_ops [1000], and > > > > compress [true] > > > > [2013-10-30 16:11:16,667][DEBUG][gateway.\*\*local.state.meta] > > > > [Burstarr] using gateway.local.auto\_import\_\*\*dangled [YES], with > > > > gateway.local.dangling\_timeout [2h] > > > > [2013-10-30 16:11:16,692][DEBUG][gateway.\*\*local.state.meta] > > > > [Burstarr] took 25ms to load state > > > > [2013-10-30 16:11:16,692][DEBUG][gateway.\*\*local.state.shards] > > > > [Burstarr] took 0s to load started shards state > > > > [2013-10-30 16:11:16,746][INFO][node] [Burstarr] > > > > initialized > > > > [2013-10-30 16:11:16,747][INFO][node] [Burstarr] > > > > starting ... > > > > [2013-10-30 16:11:16,882][INFO][transport] [Burstarr] > > > > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > > > > 10.20.4.158:9300]} > > > > [2013-10-30 16:11:16,899][TRACE][\*\*discovery] > > > > [Burstarr] waiting for 30s for the initial state to be set by the discovery > > > > [2013-10-30 16:11:19,905][TRACE][\*\*discovery.zen] > > > > [Burstarr] full ping responses: {none} > > > > [2013-10-30 16:11:19,905][DEBUG][\*\*discovery.zen] > > > > [Burstarr] filtered ping responses: (filter\_client[true], > > > > filter\_data[false]) {none} > > > > [2013-10-30 16:11:19,912][INFO][cluster.service] [Burstarr] > > > > new\_master [Burstarr][\*\*pRsc595IQfyXn24N27tbZw][inet[/\*\*10.20.4.158:9300]], > > > > reason: zen-disco-join (elected\_as\_master) > > > > [2013-10-30 16:11:19,977][TRACE][\*\*discovery] > > > > [Burstarr] initial state set from discovery > > > > [2013-10-30 16:11:19,977][INFO][discovery] [Burstarr] > > > > elasticsearch/\*\*pRsc595IQfyXn24N27tbZw > > > > [2013-10-30 16:11:20,012][INFO][http] [Burstarr] > > > > bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/ > > > > 10.20.4.158:9200]} > > > > [2013-10-30 16:11:20,012][INFO][node] [Burstarr] > > > > started > > > > [2013-10-30 16:11:20,025][INFO][gateway] [Burstarr] > > > > 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 elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@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:** ![gzion7](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@gzion7](https://discuss.elastic.co/u/gzion7)\ **Post date:** [October 31, 2013, 4:37pm UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/6 "2013-10-31T16:37:00Z")
Update: I managed to get it to work. I did not realize how finicky the YML file is with the correct spacing. I needed to add an EIP so it could check my AWS credentials on one of their sites. Can I create a NAT instance to fix this? I don't want these servers having a public IP. On Thursday, October 31, 2013 10:54:34 AM UTC-4, Gabriel Holder wrote: > This is what I've added: > cloud: > aws: > access\_key: > secret\_key: > > ``` > discovery: > type: ec2 > groups: SECURITY-GROUP > > ``` > > Unfortunately, they still don't see each other > > On Thursday, October 31, 2013 3:36:56 AM UTC-4, Norberto Meijome wrote: > > > It's all in the docs for the ec2 plugin. > > On 31/10/2013 12:51 PM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > You mean on the bottom of the file where I add my keys? I added those > > > already > > > How can I tag by security groups? > > > > > > On Wednesday, October 30, 2013 9:42:23 PM UTC-4, Norberto Meijome wrote: > > > > > > > It seems you didn't set discovery type ec2. And obviously u need to > > > > provide API keys... > > > > And you should also tell it which filter to use ( ie by tag or security > > > > group..otherwise it will attempt to connect to any of your hosts...which > > > > may be many) > > > > On 31/10/2013 7:13 AM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > > > I have two ES servers in AWS, I have security groups set to allow all > > > > > traffic from these 2 IPs. > > > > > > > > > > I installed the aws plugin. > > > > > The only changes I've made in the yml file are the cluster name, > > > > > http.max.content.length, and path to store data. > > > > > Both nodes start perfectly fine, there are no errors but they don't > > > > > discover each other. > > > > > > > > > > Here are the logs from starting ES on one of the nodes: > > > > > [2013-10-30 16:11:12,702][INFO][node] [Burstarr] > > > > > version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12:\*\*50:20Z] > > > > > [2013-10-30 16:11:12,703][INFO][node] [Burstarr] > > > > > initializing ... > > > > > [2013-10-30 16:11:12,723][INFO][plugins] [Burstarr] > > > > > loaded [cloud-aws], sites > > > > > [2013-10-30 16:11:15,199][DEBUG][\*\*discovery.zen.ping.unicast] > > > > > [Burstarr] using initial hosts , with concurrent\_connects [10] > > > > > [2013-10-30 16:11:15,202][DEBUG][\*\*discovery.zen] > > > > > [Burstarr] using ping.timeout [3s], master\_election.filter\_client [true], > > > > > master\_election.filter\_data [false] > > > > > [2013-10-30 16:11:15,203][DEBUG][\*\*discovery.zen.elect] > > > > > [Burstarr] using minimum\_master\_nodes [-1] > > > > > [2013-10-30 16:11:15,205][DEBUG][\*\*discovery.zen.fd] > > > > > [Burstarr] [master] uses ping\_interval [1s], ping\_timeout [30s], > > > > > ping\_retries [3] > > > > > [2013-10-30 16:11:15,211][DEBUG][\*\*discovery.zen.fd] > > > > > [Burstarr] [node] uses ping\_interval [1s], ping\_timeout [30s], > > > > > ping\_retries [3] > > > > > [2013-10-30 16:11:16,344][DEBUG][gateway.\*\*local] > > > > > [Burstarr] using initial\_shards [quorum], list\_timeout [30s] > > > > > [2013-10-30 16:11:16,533][DEBUG][indices.\*\*recovery] > > > > > [Burstarr] using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], > > > > > file\_chunk\_size [512kb], translog\_size [512kb], translog\_ops [1000], and > > > > > compress [true] > > > > > [2013-10-30 16:11:16,667][DEBUG][gateway.\*\*local.state.meta] > > > > > [Burstarr] using gateway.local.auto\_import\_\*\*dangled [YES], with > > > > > gateway.local.dangling\_timeout [2h] > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway.\*\*local.state.meta] > > > > > [Burstarr] took 25ms to load state > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway.\*\*local.state.shards] > > > > > [Burstarr] took 0s to load started shards state > > > > > [2013-10-30 16:11:16,746][INFO][node] [Burstarr] > > > > > initialized > > > > > [2013-10-30 16:11:16,747][INFO][node] [Burstarr] > > > > > starting ... > > > > > [2013-10-30 16:11:16,882][INFO][transport] [Burstarr] > > > > > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > > > > > 10.20.4.158:9300]} > > > > > [2013-10-30 16:11:16,899][TRACE][\*\*discovery] > > > > > [Burstarr] waiting for 30s for the initial state to be set by the discovery > > > > > [2013-10-30 16:11:19,905][TRACE][\*\*discovery.zen] > > > > > [Burstarr] full ping responses: {none} > > > > > [2013-10-30 16:11:19,905][DEBUG][\*\*discovery.zen] > > > > > [Burstarr] filtered ping responses: (filter\_client[true], > > > > > filter\_data[false]) {none} > > > > > [2013-10-30 16:11:19,912][INFO][cluster.service] [Burstarr] > > > > > new\_master [Burstarr][\*\*pRsc595IQfyXn24N27tbZw][inet[/\*\*10.20.4.158:9300]], > > > > > reason: zen-disco-join (elected\_as\_master) > > > > > [2013-10-30 16:11:19,977][TRACE][\*\*discovery] > > > > > [Burstarr] initial state set from discovery > > > > > [2013-10-30 16:11:19,977][INFO][discovery] [Burstarr] > > > > > elasticsearch/\*\*pRsc595IQfyXn24N27tbZw > > > > > [2013-10-30 16:11:20,012][INFO][http] [Burstarr] > > > > > bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/ > > > > > 10.20.4.158:9200]} > > > > > [2013-10-30 16:11:20,012][INFO][node] [Burstarr] > > > > > started > > > > > [2013-10-30 16:11:20,025][INFO][gateway] [Burstarr] > > > > > 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 elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@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:** [October 31, 2013, 10:22pm UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/7 "2013-10-31T22:22:29Z")
I don't see why you would need a public IP... Just make sure: - your instances can reach each other via the protocol used for clustering (TCP/9300 by default) - point above includes instances which may appear external to your cluster.. Across regions?.. - you API key can properly list instances (and describe tags in them if you do that ) On 01/11/2013 3:37 AM, "Gabriel Holder" [gavysdomain@gmail.com](mailto:gavysdomain@gmail.com) wrote: > Update: > I managed to get it to work. I did not realize how finicky the YML file is > with the correct spacing. > I needed to add an EIP so it could check my AWS credentials on one of > their sites. > > Can I create a NAT instance to fix this? I don't want these servers having > a public IP. > > On Thursday, October 31, 2013 10:54:34 AM UTC-4, Gabriel Holder wrote: > > > This is what I've added: > > cloud: > > aws: > > access\_key: > > secret\_key: > > > > ``` > > discovery: > > type: ec2 > > groups: SECURITY-GROUP > > > > ``` > > > > Unfortunately, they still don't see each other > > > > On Thursday, October 31, 2013 3:36:56 AM UTC-4, Norberto Meijome wrote: > > > > > It's all in the docs for the ec2 plugin. > > > On 31/10/2013 12:51 PM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > You mean on the bottom of the file where I add my keys? I added those > > > > already > > > > How can I tag by security groups? > > > > > > > > On Wednesday, October 30, 2013 9:42:23 PM UTC-4, Norberto Meijome wrote: > > > > > > > > > It seems you didn't set discovery type ec2. And obviously u need to > > > > > provide API keys... > > > > > And you should also tell it which filter to use ( ie by tag or > > > > > security group..otherwise it will attempt to connect to any of your > > > > > hosts...which may be many) > > > > > On 31/10/2013 7:13 AM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > > > > > I have two ES servers in AWS, I have security groups set to allow all > > > > > > traffic from these 2 IPs. > > > > > > > > > > > > I installed the aws plugin. > > > > > > The only changes I've made in the yml file are the cluster name, > > > > > > http.max.content.length, and path to store data. > > > > > > Both nodes start perfectly fine, there are no errors but they don't > > > > > > discover each other. > > > > > > > > > > > > Here are the logs from starting ES on one of the nodes: > > > > > > [2013-10-30 16:11:12,702][INFO][node] > > > > > > [Burstarr] version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12:\* > > > > > > _50_\*:20Z] > > > > > > [2013-10-30 16:11:12,703][INFO][node] > > > > > > [Burstarr] initializing ... > > > > > > [2013-10-30 16:11:12,723][INFO][plugins] > > > > > > [Burstarr] loaded [cloud-aws], sites > > > > > > [2013-10-30 16:11:15,199][DEBUG][**discovery**.zen.ping.unicast] > > > > > > [Burstarr] using initial hosts , with concurrent\_connects [10] > > > > > > [2013-10-30 16:11:15,202][DEBUG][**discovery**.zen] > > > > > > [Burstarr] using ping.timeout [3s], master\_election.filter\_client [true], > > > > > > master\_election.filter\_data [false] > > > > > > [2013-10-30 16:11:15,203][DEBUG][**discovery**.zen.elect] > > > > > > [Burstarr] using minimum\_master\_nodes [-1] > > > > > > [2013-10-30 16:11:15,205][DEBUG][**discovery**.zen.fd] > > > > > > [Burstarr] [master] uses ping\_interval [1s], ping\_timeout [30s], > > > > > > ping\_retries [3] > > > > > > [2013-10-30 16:11:15,211][DEBUG][**discovery**.zen.fd] > > > > > > [Burstarr] [node] uses ping\_interval [1s], ping\_timeout [30s], > > > > > > ping\_retries [3] > > > > > > [2013-10-30 16:11:16,344][DEBUG][gateway. **l** ocal] > > > > > > [Burstarr] using initial\_shards [quorum], list\_timeout [30s] > > > > > > [2013-10-30 16:11:16,533][DEBUG][indices. **r** ecovery] > > > > > > [Burstarr] using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], > > > > > > file\_chunk\_size [512kb], translog\_size [512kb], translog\_ops [1000], and > > > > > > compress [true] > > > > > > [2013-10-30 16:11:16,667][DEBUG][gateway. **l** ocal.state.meta] > > > > > > [Burstarr] using gateway.local.auto\_import\_ **dang** led [YES], with > > > > > > gateway.local.dangling\_timeout [2h] > > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway. **l** ocal.state.meta] > > > > > > [Burstarr] took 25ms to load state > > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway. **l** ocal.state.shards] > > > > > > [Burstarr] took 0s to load started shards state > > > > > > [2013-10-30 16:11:16,746][INFO][node] > > > > > > [Burstarr] initialized > > > > > > [2013-10-30 16:11:16,747][INFO][node] > > > > > > [Burstarr] starting ... > > > > > > [2013-10-30 16:11:16,882][INFO][transport] > > > > > > [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address > > > > > > {inet[/10.20.4.158:9300]} > > > > > > [2013-10-30 16:11:16,899][TRACE][**discovery**] > > > > > > [Burstarr] waiting for 30s for the initial state to be set by the discovery > > > > > > [2013-10-30 16:11:19,905][TRACE][**discovery**.zen] > > > > > > [Burstarr] full ping responses: {none} > > > > > > [2013-10-30 16:11:19,905][DEBUG][**discovery**.zen] > > > > > > [Burstarr] filtered ping responses: (filter\_client[true], > > > > > > filter\_data[false]) {none} > > > > > > [2013-10-30 16:11:19,912][INFO][cluster.service] > > > > > > [Burstarr] new\_master [Burstarr][**pRsc595IQfyXn24N27t** bZw][inet[/\*\* > > > > > > 10.20.4.158:9300]], reason: zen-disco-join (elected\_as\_master) > > > > > > [2013-10-30 16:11:19,977][TRACE][**discovery**] > > > > > > [Burstarr] initial state set from discovery > > > > > > [2013-10-30 16:11:19,977][INFO][discovery] > > > > > > [Burstarr] elasticsearch/ **pRsc595IQfyXn24N** 27tbZw > > > > > > [2013-10-30 16:11:20,012][INFO][http] > > > > > > [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address > > > > > > {inet[/10.20.4.158:9200]} > > > > > > [2013-10-30 16:11:20,012][INFO][node] > > > > > > [Burstarr] started > > > > > > [2013-10-30 16:11:20,025][INFO][gateway] > > > > > > [Burstarr] 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 elasticsearc...@\*\*googlegroups.\*\*com. > > > > > > For more options, visit [https://groups.google.com/\*\*grou\*\*ps/opt\_out](https://groups.google.com/ **grou** ps/opt_out)[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 elasticsearc...@googlegroups.\*\*com. > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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). -- 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:** ![gzion7](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@gzion7](https://discuss.elastic.co/u/gzion7)\ **Post date:** [October 31, 2013, 10:39pm UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/8 "2013-10-31T22:39:50Z")
1. I can telnet just fine to 9200, I'll have to test 9300. 2. These are within the same region. 3. Do you mean running ec2-describe-instances from the command line? I think the reason why I need a public IP is because it tries to validate my AWS credentials on their site. This could just be because at this moment I don't have a NAT instance setup so I had to actually add the discovery: ec2...etc part. In my previous setup I didn't need to specify discovery:ec2 part in my config with the NAT instance. They were able to see each other simply because of the AWS Plugin. On Thursday, October 31, 2013 6:22:29 PM UTC-4, Norberto Meijome wrote: > I don't see why you would need a public IP... Just make sure: > > - your instances can reach each other via the protocol used for clustering > (TCP/9300 by default) > - point above includes instances which may appear external to your > cluster.. Across regions?.. > - you API key can properly list instances (and describe tags in them if > you do that ) > On 01/11/2013 3:37 AM, "Gabriel Holder" \<[gavys...@gmail.com](mailto:gavys...@gmail.com) \\> > wrote: > > > Update: > > I managed to get it to work. I did not realize how finicky the YML file > > is with the correct spacing. > > I needed to add an EIP so it could check my AWS credentials on one of > > their sites. > > > > Can I create a NAT instance to fix this? I don't want these servers > > having a public IP. > > > > On Thursday, October 31, 2013 10:54:34 AM UTC-4, Gabriel Holder wrote: > > > > > This is what I've added: > > > cloud: > > > aws: > > > access\_key: > > > secret\_key: > > > > > > ``` > > > discovery: > > > type: ec2 > > > groups: SECURITY-GROUP > > > > > > ``` > > > > > > Unfortunately, they still don't see each other > > > > > > On Thursday, October 31, 2013 3:36:56 AM UTC-4, Norberto Meijome wrote: > > > > > > > It's all in the docs for the ec2 plugin. > > > > On 31/10/2013 12:51 PM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > > > You mean on the bottom of the file where I add my keys? I added those > > > > > already > > > > > How can I tag by security groups? > > > > > > > > > > On Wednesday, October 30, 2013 9:42:23 PM UTC-4, Norberto Meijome > > > > > wrote: > > > > > > > > > > > It seems you didn't set discovery type ec2. And obviously u need to > > > > > > provide API keys... > > > > > > And you should also tell it which filter to use ( ie by tag or > > > > > > security group..otherwise it will attempt to connect to any of your > > > > > > hosts...which may be many) > > > > > > On 31/10/2013 7:13 AM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > > > > > > > I have two ES servers in AWS, I have security groups set to allow > > > > > > > all traffic from these 2 IPs. > > > > > > > > > > > > > > I installed the aws plugin. > > > > > > > The only changes I've made in the yml file are the cluster name, > > > > > > > http.max.content.length, and path to store data. > > > > > > > Both nodes start perfectly fine, there are no errors but they don't > > > > > > > discover each other. > > > > > > > > > > > > > > Here are the logs from starting ES on one of the nodes: > > > > > > > [2013-10-30 16:11:12,702][INFO][node] > > > > > > > [Burstarr] version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12: > > > > > > > **50** :20Z] > > > > > > > [2013-10-30 16:11:12,703][INFO][node] > > > > > > > [Burstarr] initializing ... > > > > > > > [2013-10-30 16:11:12,723][INFO][plugins] > > > > > > > [Burstarr] loaded [cloud-aws], sites > > > > > > > [2013-10-30 16:11:15,199][DEBUG][**discovery**.zen.ping.unicast] > > > > > > > [Burstarr] using initial hosts , with concurrent\_connects [10] > > > > > > > [2013-10-30 16:11:15,202][DEBUG][**discovery**.zen] > > > > > > > [Burstarr] using ping.timeout [3s], master\_election.filter\_client [true], > > > > > > > master\_election.filter\_data [false] > > > > > > > [2013-10-30 16:11:15,203][DEBUG][**discovery**.zen.elect] > > > > > > > [Burstarr] using minimum\_master\_nodes [-1] > > > > > > > [2013-10-30 16:11:15,205][DEBUG][**discovery**.zen.fd] > > > > > > > [Burstarr] [master] uses ping\_interval [1s], ping\_timeout [30s], > > > > > > > ping\_retries [3] > > > > > > > [2013-10-30 16:11:15,211][DEBUG][**discovery**.zen.fd] > > > > > > > [Burstarr] [node] uses ping\_interval [1s], ping\_timeout [30s], > > > > > > > ping\_retries [3] > > > > > > > [2013-10-30 16:11:16,344][DEBUG][gateway. **l** ocal] > > > > > > > [Burstarr] using initial\_shards [quorum], list\_timeout [30s] > > > > > > > [2013-10-30 16:11:16,533][DEBUG][indices. **r** ecovery] > > > > > > > [Burstarr] using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], > > > > > > > file\_chunk\_size [512kb], translog\_size [512kb], translog\_ops [1000], and > > > > > > > compress [true] > > > > > > > [2013-10-30 16:11:16,667][DEBUG][gateway. **l** ocal.state.meta] > > > > > > > [Burstarr] using gateway.local.auto\_import\_ **dang** led [YES], with > > > > > > > gateway.local.dangling\_timeout [2h] > > > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway. **l** ocal.state.meta] > > > > > > > [Burstarr] took 25ms to load state > > > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway. **l** ocal.state.shards] > > > > > > > [Burstarr] took 0s to load started shards state > > > > > > > [2013-10-30 16:11:16,746][INFO][node] > > > > > > > [Burstarr] initialized > > > > > > > [2013-10-30 16:11:16,747][INFO][node] > > > > > > > [Burstarr] starting ... > > > > > > > [2013-10-30 16:11:16,882][INFO][transport] > > > > > > > [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address > > > > > > > {inet[/10.20.4.158:9300]} > > > > > > > [2013-10-30 16:11:16,899][TRACE][**discovery**] > > > > > > > [Burstarr] waiting for 30s for the initial state to be set by the discovery > > > > > > > [2013-10-30 16:11:19,905][TRACE][**discovery**.zen] > > > > > > > [Burstarr] full ping responses: {none} > > > > > > > [2013-10-30 16:11:19,905][DEBUG][**discovery**.zen] > > > > > > > [Burstarr] filtered ping responses: (filter\_client[true], > > > > > > > filter\_data[false]) {none} > > > > > > > [2013-10-30 16:11:19,912][INFO][cluster.service] > > > > > > > [Burstarr] new\_master [Burstarr][**pRsc595IQfyXn24N27t** bZw][inet[/\* > > > > > > > \*10.20.4.158:9300]], reason: zen-disco-join (elected\_as\_master) > > > > > > > [2013-10-30 16:11:19,977][TRACE][**discovery**] > > > > > > > [Burstarr] initial state set from discovery > > > > > > > [2013-10-30 16:11:19,977][INFO][discovery] > > > > > > > [Burstarr] elasticsearch/ **pRsc595IQfyXn24N** 27tbZw > > > > > > > [2013-10-30 16:11:20,012][INFO][http] > > > > > > > [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address > > > > > > > {inet[/10.20.4.158:9200]} > > > > > > > [2013-10-30 16:11:20,012][INFO][node] > > > > > > > [Burstarr] started > > > > > > > [2013-10-30 16:11:20,025][INFO][gateway] > > > > > > > [Burstarr] 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 elasticsearc...@\*\*googlegroups.\*\*com. > > > > > > > For more options, visit [https://groups.google.com/\*\*grou\*\*ps/opt\_out](https://groups.google.com/ **grou** ps/opt_out)[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 elasticsearc...@googlegroups.\*\*com. > > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@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:** [November 1, 2013, 2:15am UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/9 "2013-11-01T02:15:58Z")
9200 is http API port. Clustering goes over 9300 ( by default) I mean the API key you use has to be able to get the information it needs to find servers to speak to. It does this by connecting to AWS API and listing instances filtered by what you tell it in the config. But yes, you should be able to get this information manually from the CLI , as a debugging step. On 01/11/2013 9:39 AM, "Gabriel Holder" [gavysdomain@gmail.com](mailto:gavysdomain@gmail.com) wrote: > 1. I can telnet just fine to 9200, I'll have to test 9300. > 2. These are within the same region. > 3. Do you mean running ec2-describe-instances from the command line? > > I think the reason why I need a public IP is because it tries to validate > my AWS credentials on their site. This could just be because at this moment > I don't have a > NAT instance setup so I had to actually add the discovery: ec2...etc part. > > In my previous setup I didn't need to specify discovery:ec2 part in my > config with the NAT instance. They were able to see each other simply > because of the AWS Plugin. > > On Thursday, October 31, 2013 6:22:29 PM UTC-4, Norberto Meijome wrote: > > > I don't see why you would need a public IP... Just make sure: > > > > - your instances can reach each other via the protocol used for > > clustering (TCP/9300 by default) > > - point above includes instances which may appear external to your > > cluster.. Across regions?.. > > - you API key can properly list instances (and describe tags in them if > > you do that ) > > On 01/11/2013 3:37 AM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > Update: > > > I managed to get it to work. I did not realize how finicky the YML file > > > is with the correct spacing. > > > I needed to add an EIP so it could check my AWS credentials on one of > > > their sites. > > > > > > Can I create a NAT instance to fix this? I don't want these servers > > > having a public IP. > > > > > > On Thursday, October 31, 2013 10:54:34 AM UTC-4, Gabriel Holder wrote: > > > > > > > This is what I've added: > > > > cloud: > > > > aws: > > > > access\_key: > > > > secret\_key: > > > > > > > > ``` > > > > discovery: > > > > type: ec2 > > > > groups: SECURITY-GROUP > > > > > > > > ``` > > > > > > > > Unfortunately, they still don't see each other > > > > > > > > On Thursday, October 31, 2013 3:36:56 AM UTC-4, Norberto Meijome wrote: > > > > > > > > > It's all in the docs for the ec2 plugin. > > > > > On 31/10/2013 12:51 PM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > > > > > You mean on the bottom of the file where I add my keys? I added those > > > > > > already > > > > > > How can I tag by security groups? > > > > > > > > > > > > On Wednesday, October 30, 2013 9:42:23 PM UTC-4, Norberto Meijome > > > > > > wrote: > > > > > > > > > > > > > It seems you didn't set discovery type ec2. And obviously u need to > > > > > > > provide API keys... > > > > > > > And you should also tell it which filter to use ( ie by tag or > > > > > > > security group..otherwise it will attempt to connect to any of your > > > > > > > hosts...which may be many) > > > > > > > On 31/10/2013 7:13 AM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > > > > > > > > > I have two ES servers in AWS, I have security groups set to allow > > > > > > > > all traffic from these 2 IPs. > > > > > > > > > > > > > > > > I installed the aws plugin. > > > > > > > > The only changes I've made in the yml file are the cluster name, > > > > > > > > http.max.content.length, and path to store data. > > > > > > > > Both nodes start perfectly fine, there are no errors but they don't > > > > > > > > discover each other. > > > > > > > > > > > > > > > > Here are the logs from starting ES on one of the nodes: > > > > > > > > [2013-10-30 16:11:12,702][INFO][node] > > > > > > > > [Burstarr] version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12: > > > > > > > > **50** \*\*:20Z] > > > > > > > > [2013-10-30 16:11:12,703][INFO][node] > > > > > > > > [Burstarr] initializing ... > > > > > > > > [2013-10-30 16:11:12,723][INFO][plugins] > > > > > > > > [Burstarr] loaded [cloud-aws], sites > > > > > > > > [2013-10-30 16:11:15,199][DEBUG][**discovery** \*\*.zen.ping.unicast] > > > > > > > > [Burstarr] using initial hosts , with concurrent\_connects [10] > > > > > > > > [2013-10-30 16:11:15,202][DEBUG][**discovery** \*\*.zen] > > > > > > > > [Burstarr] using ping.timeout [3s], master\_election.filter\_client [true], > > > > > > > > master\_election.filter\_data [false] > > > > > > > > [2013-10-30 16:11:15,203][DEBUG][**discovery** \*\*.zen.elect] > > > > > > > > [Burstarr] using minimum\_master\_nodes [-1] > > > > > > > > [2013-10-30 16:11:15,205][DEBUG][**discovery** \*\*.zen.fd] > > > > > > > > [Burstarr] [master] uses ping\_interval [1s], ping\_timeout [30s], > > > > > > > > ping\_retries [3] > > > > > > > > [2013-10-30 16:11:15,211][DEBUG][**discovery** \*\*.zen.fd] > > > > > > > > [Burstarr] [node] uses ping\_interval [1s], ping\_timeout [30s], > > > > > > > > ping\_retries [3] > > > > > > > > [2013-10-30 16:11:16,344][DEBUG][gateway.**local] > > > > > > > > [Burstarr] using initial\_shards [quorum], list\_timeout [30s] > > > > > > > > [2013-10-30 16:11:16,533][DEBUG][indices.\*\*recovery] > > > > > > > > [Burstarr] using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], > > > > > > > > file\_chunk\_size [512kb], translog\_size [512kb], translog\_ops [1000], and > > > > > > > > compress [true] > > > > > > > > [2013-10-30 16:11:16,667][DEBUG][gateway.local.state.meta] > > > > > > > > [Burstarr] using gateway.local.auto\_import\_\*\*dangled [YES], > > > > > > > > with gateway.local.dangling\_timeout [2h] > > > > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway.local.state.meta] > > > > > > > > [Burstarr] took 25ms to load state > > > > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway.\*\*local.state.shards] > > > > > > > > [Burstarr] took 0s to load started shards state > > > > > > > > [2013-10-30 16:11:16,746][INFO][node] > > > > > > > > [Burstarr] initialized > > > > > > > > [2013-10-30 16:11:16,747][INFO][node] > > > > > > > > [Burstarr] starting ... > > > > > > > > [2013-10-30 16:11:16,882][INFO][transport] > > > > > > > > [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address > > > > > > > > {inet[/10.20.4.158:9300]} > > > > > > > > [2013-10-30 16:11:16,899][TRACE][discovery] > > > > > > > > [Burstarr] waiting for 30s for the initial state to be set by the discovery > > > > > > > > [2013-10-30 16:11:19,905][TRACE][discovery.zen] > > > > > > > > [Burstarr] full ping responses: {none} > > > > > > > > [2013-10-30 16:11:19,905][DEBUG][discovery**.zen] > > > > > > > > [Burstarr] filtered ping responses: (filter\_client[true], > > > > > > > > filter\_data[false]) {none} > > > > > > > > [2013-10-30 16:11:19,912][INFO][cluster.service] > > > > > > > > [Burstarr] new\_master [Burstarr][ **pRsc595IQfyXn24N27t** \*\* > > > > > > > > bZw][inet[/**10.20.4.158:9300]], reason: zen-disco-join > > > > > > > > (elected\_as\_master) > > > > > > > > [2013-10-30 16:11:19,977][TRACE][discovery**] > > > > > > > > [Burstarr] initial state set from discovery > > > > > > > > [2013-10-30 16:11:19,977][INFO][discovery] > > > > > > > > [Burstarr] elasticsearch/\*\*pRsc595IQfyXn24N\*\*\*\*27tbZw > > > > > > > > [2013-10-30 16:11:20,012][INFO][http] > > > > > > > > [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address > > > > > > > > {inet[/10.20.4.158:9200]} > > > > > > > > [2013-10-30 16:11:20,012][INFO][node] > > > > > > > > [Burstarr] started > > > > > > > > [2013-10-30 16:11:20,025][INFO][gateway] > > > > > > > > [Burstarr] 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 elasticsearc...@**googlegroups.com. > > > > > > > > For more options, visit [https://groups.google.com/\*\*grou](https://groups.google.com/**grou)**\*\* > > > > > > > > ps/opt\_out [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 elasticsearc...@googlegroups. **c** om. > > > > > > > For more options, visit [https://groups.google.com/\*\*grou\*\*ps/opt\_out](https://groups.google.com/ **grou** ps/opt_out)[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 elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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). -- 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:** ![gzion7](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@gzion7](https://discuss.elastic.co/u/gzion7)\ **Post date:** [November 1, 2013, 2:25am UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/10 "2013-11-01T02:25:52Z")
I'll test 9300 when I get the chance. When I didn't have the instances assigned an EIP they would generate an error saying unable to connect to "ec2.aws.." or something (I don't have the exact error at hand). I believe the EIP allows it to check my AWS credentials and validate them and then allows the nodes to see each other. These servers ideally should only be able to access what is specified in the security groups. This is my first time having to actually specify the discovery.ec2 option to my apologies for the confusion. In my old setup we had a NAT instance and didn't need the discovery:ec2 option. On Thursday, October 31, 2013 10:15:58 PM UTC-4, Norberto Meijome wrote: > 9200 is http API port. Clustering goes over 9300 ( by default) > I mean the API key you use has to be able to get the information it needs > to find servers to speak to. It does this by connecting to AWS API and > listing instances filtered by what you tell it in the config. But yes, you > should be able to get this information manually from the CLI , as a > debugging step. > On 01/11/2013 9:39 AM, "Gabriel Holder" \<[gavys...@gmail.com](mailto:gavys...@gmail.com) \\> > wrote: > > > 1. I can telnet just fine to 9200, I'll have to test 9300. > > 2. These are within the same region. > > 3. Do you mean running ec2-describe-instances from the command line? > > > > I think the reason why I need a public IP is because it tries to validate > > my AWS credentials on their site. This could just be because at this moment > > I don't have a > > NAT instance setup so I had to actually add the discovery: ec2...etc part. > > > > In my previous setup I didn't need to specify discovery:ec2 part in my > > config with the NAT instance. They were able to see each other simply > > because of the AWS Plugin. > > > > On Thursday, October 31, 2013 6:22:29 PM UTC-4, Norberto Meijome wrote: > > > > > I don't see why you would need a public IP... Just make sure: > > > > > > - your instances can reach each other via the protocol used for > > > clustering (TCP/9300 by default) > > > - point above includes instances which may appear external to your > > > cluster.. Across regions?.. > > > - you API key can properly list instances (and describe tags in them if > > > you do that ) > > > On 01/11/2013 3:37 AM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > Update: > > > > I managed to get it to work. I did not realize how finicky the YML file > > > > is with the correct spacing. > > > > I needed to add an EIP so it could check my AWS credentials on one of > > > > their sites. > > > > > > > > Can I create a NAT instance to fix this? I don't want these servers > > > > having a public IP. > > > > > > > > On Thursday, October 31, 2013 10:54:34 AM UTC-4, Gabriel Holder wrote: > > > > > > > > > This is what I've added: > > > > > cloud: > > > > > aws: > > > > > access\_key: > > > > > secret\_key: > > > > > > > > > > ``` > > > > > discovery: > > > > > type: ec2 > > > > > groups: SECURITY-GROUP > > > > > > > > > > ``` > > > > > > > > > > Unfortunately, they still don't see each other > > > > > > > > > > On Thursday, October 31, 2013 3:36:56 AM UTC-4, Norberto Meijome wrote: > > > > > > > > > > > It's all in the docs for the ec2 plugin. > > > > > > On 31/10/2013 12:51 PM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > > > > > > > You mean on the bottom of the file where I add my keys? I added > > > > > > > those already > > > > > > > How can I tag by security groups? > > > > > > > > > > > > > > On Wednesday, October 30, 2013 9:42:23 PM UTC-4, Norberto Meijome > > > > > > > wrote: > > > > > > > > > > > > > > > It seems you didn't set discovery type ec2. And obviously u need to > > > > > > > > provide API keys... > > > > > > > > And you should also tell it which filter to use ( ie by tag or > > > > > > > > security group..otherwise it will attempt to connect to any of your > > > > > > > > hosts...which may be many) > > > > > > > > On 31/10/2013 7:13 AM, "Gabriel Holder" [gavys...@gmail.com](mailto:gavys...@gmail.com) wrote: > > > > > > > > > > > > > > > > > I have two ES servers in AWS, I have security groups set to allow > > > > > > > > > all traffic from these 2 IPs. > > > > > > > > > > > > > > > > > > I installed the aws plugin. > > > > > > > > > The only changes I've made in the yml file are the cluster name, > > > > > > > > > http.max.content.length, and path to store data. > > > > > > > > > Both nodes start perfectly fine, there are no errors but they > > > > > > > > > don't discover each other. > > > > > > > > > > > > > > > > > > Here are the logs from starting ES on one of the nodes: > > > > > > > > > [2013-10-30 16:11:12,702][INFO][node] > > > > > > > > > [Burstarr] version[0.90.5], pid[25867], build[c8714e8/2013-09-17T12: > > > > > > > > > **50** \*\*:20Z] > > > > > > > > > [2013-10-30 16:11:12,703][INFO][node] > > > > > > > > > [Burstarr] initializing ... > > > > > > > > > [2013-10-30 16:11:12,723][INFO][plugins] > > > > > > > > > [Burstarr] loaded [cloud-aws], sites > > > > > > > > > [2013-10-30 16:11:15,199][DEBUG][**discovery** \*\*.zen.ping.unicast] > > > > > > > > > [Burstarr] using initial hosts , with concurrent\_connects [10] > > > > > > > > > [2013-10-30 16:11:15,202][DEBUG][**discovery** \*\*.zen] > > > > > > > > > [Burstarr] using ping.timeout [3s], master\_election.filter\_client [true], > > > > > > > > > master\_election.filter\_data [false] > > > > > > > > > [2013-10-30 16:11:15,203][DEBUG][**discovery** \*\*.zen.elect] > > > > > > > > > [Burstarr] using minimum\_master\_nodes [-1] > > > > > > > > > [2013-10-30 16:11:15,205][DEBUG][**discovery** \*\*.zen.fd] > > > > > > > > > [Burstarr] [master] uses ping\_interval [1s], ping\_timeout [30s], > > > > > > > > > ping\_retries [3] > > > > > > > > > [2013-10-30 16:11:15,211][DEBUG][**discovery** \*\*.zen.fd] > > > > > > > > > [Burstarr] [node] uses ping\_interval [1s], ping\_timeout [30s], > > > > > > > > > ping\_retries [3] > > > > > > > > > [2013-10-30 16:11:16,344][DEBUG][gateway.**local] > > > > > > > > > [Burstarr] using initial\_shards [quorum], list\_timeout [30s] > > > > > > > > > [2013-10-30 16:11:16,533][DEBUG][indices.\*\*recovery] > > > > > > > > > [Burstarr] using max\_bytes\_per\_sec[20mb], concurrent\_streams [3], > > > > > > > > > file\_chunk\_size [512kb], translog\_size [512kb], translog\_ops [1000], and > > > > > > > > > compress [true] > > > > > > > > > [2013-10-30 16:11:16,667][DEBUG][gateway.local.state.meta] > > > > > > > > > [Burstarr] using gateway.local.auto\_import\_\*\*dangled [YES], > > > > > > > > > with gateway.local.dangling\_timeout [2h] > > > > > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway.local.state.meta] > > > > > > > > > [Burstarr] took 25ms to load state > > > > > > > > > [2013-10-30 16:11:16,692][DEBUG][gateway.\*\*local.state.shards] > > > > > > > > > [Burstarr] took 0s to load started shards state > > > > > > > > > [2013-10-30 16:11:16,746][INFO][node] > > > > > > > > > [Burstarr] initialized > > > > > > > > > [2013-10-30 16:11:16,747][INFO][node] > > > > > > > > > [Burstarr] starting ... > > > > > > > > > [2013-10-30 16:11:16,882][INFO][transport] > > > > > > > > > [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address > > > > > > > > > {inet[/10.20.4.158:9300]} > > > > > > > > > [2013-10-30 16:11:16,899][TRACE][discovery] > > > > > > > > > [Burstarr] waiting for 30s for the initial state to be set by the discovery > > > > > > > > > [2013-10-30 16:11:19,905][TRACE][discovery.zen] > > > > > > > > > [Burstarr] full ping responses: {none} > > > > > > > > > [2013-10-30 16:11:19,905][DEBUG][discovery**.zen] > > > > > > > > > [Burstarr] filtered ping responses: (filter\_client[true], > > > > > > > > > filter\_data[false]) {none} > > > > > > > > > [2013-10-30 16:11:19,912][INFO][cluster.service] > > > > > > > > > [Burstarr] new\_master [Burstarr][ **pRsc595IQfyXn24N27t** \*\* > > > > > > > > > bZw][inet[/**10.20.4.158:9300]], reason: zen-disco-join > > > > > > > > > (elected\_as\_master) > > > > > > > > > [2013-10-30 16:11:19,977][TRACE][discovery**] > > > > > > > > > [Burstarr] initial state set from discovery > > > > > > > > > [2013-10-30 16:11:19,977][INFO][discovery] > > > > > > > > > [Burstarr] elasticsearch/\*\*pRsc595IQfyXn24N\*\*\*\*27tbZw > > > > > > > > > [2013-10-30 16:11:20,012][INFO][http] > > > > > > > > > [Burstarr] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address > > > > > > > > > {inet[/10.20.4.158:9200]} > > > > > > > > > [2013-10-30 16:11:20,012][INFO][node] > > > > > > > > > [Burstarr] started > > > > > > > > > [2013-10-30 16:11:20,025][INFO][gateway] > > > > > > > > > [Burstarr] 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 elasticsearc...@**googlegroups.com. > > > > > > > > > For more options, visit [https://groups.google.com/\*\*grou](https://groups.google.com/**grou)**\*\* > > > > > > > > > ps/opt\_out [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 elasticsearc...@googlegroups. **c** om. > > > > > > > > For more options, visit [https://groups.google.com/\*\*grou\*\*ps/opt\_out](https://groups.google.com/ **grou** ps/opt_out)[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 elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@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:09am UTC](https://discuss.elastic.co/t/aws-nodes-dont-discover-each-other/14177/11 "2017-07-06T02:09:26Z")