# Problem with cluster setup in AWS **URL:** \ **Category:** Elasticsearch\ **Created:** [June 14, 2012, 11:35am UTC](https://discuss.elastic.co/t/problem-with-cluster-setup-in-aws/8102 "2012-06-14T11:35:17Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![rohit\_reddy](https://avatars.discourse-cdn.com/v4/letter/r/ed655f/32.png) [@rohit\_reddy](https://discuss.elastic.co/u/rohit_reddy)\ **Post date:** [June 14, 2012, 11:35am UTC](https://discuss.elastic.co/t/problem-with-cluster-setup-in-aws/8102/1 "2012-06-14T11:35:17Z")
Hi, I'm experimenting with elastic search on AWS. I'm following the tutorial " [http://www.elasticsearch.org/tutorials/2011/08/22/elasticsearch-on-ec2.html](http://www.elasticsearch.org/tutorials/2011/08/22/elasticsearch-on-ec2.html) ". I was able to successfully set up the elasticsearch instance on 1 Instance. But having problem setting it up of 2 instances. That is the 2 node is not able to discover the first node. Both are up independently but replication is not happening. I have used all the default configurations (5 shards and 1 replica) and just changed the following properties. I using local storage, did not configure s3 gateway cluster.name: iv-search cloud: aws: access\_key: secret\_key: discovery: type: ec2 cloud.aws.region: us-east-1 I have also opened 22, 9300 and 9200 ports. This is the my first time with both AWS and elasticsearch. So any help would be great. LOGS: [2012-06-14 07:07:14,798][INFO][node] [Xavin] {0.19.4}[2355]: started [2012-06-14 07:07:14,810][INFO][gateway] [Xavin] recovered [0] indices into cluster\_state [2012-06-14 09:40:18,845][INFO][node] [Zeus] {0.19.4}[2515]: initializing ... [2012-06-14 09:40:18,859][INFO][plugins] [Zeus] loaded [cloud-aws], sites [] [2012-06-14 09:40:20,236][DEBUG][discovery.zen.ping.multicast] [Zeus] using group [224.2.2.4], with port [54328], ttl [3], and address [null] [2012-06-14 09:40:20,239][DEBUG][discovery.zen.ping.unicast] [Zeus] using initial hosts [], with concurrent\_connects [10] [2012-06-14 09:40:20,240][DEBUG][discovery.zen] [Zeus] using ping.timeout [3s] [2012-06-14 09:40:20,245][DEBUG][discovery.zen.elect] [Zeus] using minimum\_master\_nodes [-1] [2012-06-14 09:40:20,246][DEBUG][discovery.zen.fd] [Zeus] [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2012-06-14 09:40:20,250][DEBUG][discovery.zen.fd] [Zeus] [node] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] [2012-06-14 09:40:21,298][DEBUG][gateway.local] [Zeus] using initial\_shards [quorum], list\_timeout [30s] [2012-06-14 09:40:21,538][DEBUG][gateway.local.state.shards] [Zeus] took 0s to load started shards state [2012-06-14 09:40:21,540][DEBUG][gateway.local.state.meta] [Zeus] took 0s to load state [2012-06-14 09:40:21,603][INFO][node] [Zeus] {0.19.4}[2515]: initialized [2012-06-14 09:40:21,604][INFO][node] [Zeus] {0.19.4}[2515]: starting ... [2012-06-14 09:40:21,685][INFO][transport] [Zeus] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/10.2.5.143:9300]} [2012-06-14 09:40:21,697][TRACE][discovery] [Zeus] waiting for 30s for the initial state to be set by the discovery [2012-06-14 09:40:21,725][TRACE][discovery.zen.ping.multicast] [Zeus] [1] sending ping request [2012-06-14 09:40:23,227][TRACE][discovery.zen.ping.multicast] [Zeus] [1] sending ping request [2012-06-14 09:40:24,729][DEBUG][discovery.zen] [Zeus] ping responses: {none} [2012-06-14 09:40:24,734][INFO][cluster.service] [Zeus] new\_master [Zeus][secret][inet[/10.2.5.143:9300]], reason: zen-disco-join (elected\_as\_master) [2012-06-14 09:40:24,801][TRACE][discovery] [Zeus] initial state set from discovery [2012-06-14 09:40:24,802][INFO][discovery] [Zeus] iv-search/ [2012-06-14 09:40:24,816][INFO][gateway] [Zeus] recovered [0] indices into cluster\_state [2012-06-14 09:40:24,818][INFO][http] [Zeus] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/10.2.5.143:9200]} [2012-06-14 09:40:24,818][INFO][node] [Zeus] {0.19.4}[2515]: started Thanks Rohit ---
**Author:** ![benny\_sadeh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benny_sadeh/32/2797_2.png) [@benny\_sadeh](https://discuss.elastic.co/u/benny_sadeh)\ **Post date:** [June 19, 2012, 1:50pm UTC](https://discuss.elastic.co/t/problem-with-cluster-setup-in-aws/8102/2 "2012-06-19T13:50:27Z")
your issue might be security-group related. so first, just try allowing access to all, not just the security group on ports 9200 & 9300. if that solves the problem and you still want to restrict access, browse the mailing list for related advice. Benny On Thursday, June 14, 2012 4:35:17 AM UTC-7, rohit reddy wrote: > Hi, > > I'm experimenting with Elasticsearch on AWS. I'm following the tutorial > " > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/tutorials/2011/08/22/elasticsearch-on-ec2.html) > ". > > I was able to successfully set up the elasticsearch instance on 1 > Instance. But having problem setting it up of 2 instances. That is the 2 > node is not able to discover the first node. > Both are up independently but replication is not happening. > > I have used all the default configurations (5 shards and 1 replica) and > just changed the following properties. I using local storage, did not > configure s3 gateway > > cluster.name: iv-search > > cloud: > aws: > access\_key: > secret\_key: > discovery: > type: ec2 > cloud.aws.region: us-east-1 > > I have also opened 22, 9300 and 9200 ports. > This is the my first time with both AWS and elasticsearch. So any help > would be great. > > LOGS: > > [2012-06-14 07:07:14,798][INFO][node] [Xavin] > {0.19.4}[2355]: started > [2012-06-14 07:07:14,810][INFO][gateway] [Xavin] > recovered [0] indices into cluster\_state > [2012-06-14 09:40:18,845][INFO][node] [Zeus] > {0.19.4}[2515]: initializing ... > [2012-06-14 09:40:18,859][INFO][plugins] [Zeus] loaded > [cloud-aws], sites > [2012-06-14 09:40:20,236][DEBUG][discovery.zen.ping.multicast] [Zeus] > using group [224.2.2.4], with port [54328], ttl [3], and address [null] > [2012-06-14 09:40:20,239][DEBUG][discovery.zen.ping.unicast] [Zeus] using > initial hosts , with concurrent\_connects [10] > [2012-06-14 09:40:20,240][DEBUG][discovery.zen] [Zeus] using > ping.timeout [3s] > [2012-06-14 09:40:20,245][DEBUG][discovery.zen.elect] [Zeus] using > minimum\_master\_nodes [-1] > [2012-06-14 09:40:20,246][DEBUG][discovery.zen.fd] [Zeus] > [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > [2012-06-14 09:40:20,250][DEBUG][discovery.zen.fd] [Zeus] [node > ] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > [2012-06-14 09:40:21,298][DEBUG][gateway.local] [Zeus] using > initial\_shards [quorum], list\_timeout [30s] > [2012-06-14 09:40:21,538][DEBUG][gateway.local.state.shards] [Zeus] took > 0s to load started shards state > [2012-06-14 09:40:21,540][DEBUG][gateway.local.state.meta] [Zeus] took 0s > to load state > [2012-06-14 09:40:21,603][INFO][node] [Zeus] > {0.19.4}[2515]: initialized > [2012-06-14 09:40:21,604][INFO][node] [Zeus] > {0.19.4}[2515]: starting ... > [2012-06-14 09:40:21,685][INFO][transport] [Zeus] > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > 10.2.5.143:9300]} > [2012-06-14 09:40:21,697][TRACE][discovery] [Zeus] waiting > for 30s for the initial state to be set by the discovery > [2012-06-14 09:40:21,725][TRACE][discovery.zen.ping.multicast] [Zeus] [1] > sending ping request > [2012-06-14 09:40:23,227][TRACE][discovery.zen.ping.multicast] [Zeus] [1] > sending ping request > [2012-06-14 09:40:24,729][DEBUG][discovery.zen] [Zeus] ping > responses: {none} > [2012-06-14 09:40:24,734][INFO][cluster.service] [Zeus] > new\_master [Zeus][secret][inet[/10.2.5.143:9300]], reason: zen-disco-join > (elected\_as\_master) > [2012-06-14 09:40:24,801][TRACE][discovery] [Zeus] initial > state set from discovery > [2012-06-14 09:40:24,802][INFO][discovery] [Zeus] > iv-search/ > [2012-06-14 09:40:24,816][INFO][gateway] [Zeus] > recovered [0] indices into cluster\_state > [2012-06-14 09:40:24,818][INFO][http] [Zeus] > bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/ > 10.2.5.143:9200]} > [2012-06-14 09:40:24,818][INFO][node] [Zeus] > {0.19.4}[2515]: started > > Thanks > Rohit ---
**Author:** ![rohit\_reddy](https://avatars.discourse-cdn.com/v4/letter/r/ed655f/32.png) [@rohit\_reddy](https://discuss.elastic.co/u/rohit_reddy)\ **Post date:** [June 20, 2012, 8:26am UTC](https://discuss.elastic.co/t/problem-with-cluster-setup-in-aws/8102/3 "2012-06-20T08:26:53Z")
Thanks for the reply. The setup started working when i used the versions mentioned in the tutorial. i.e., elasticsearch : 0.19.0 elasticsearch-cloud-aws : 1.4.0 It was not working with elasticsearch 0.19.4 and cloud-aws 1.6.0. Did the configurations change in these versions. I search the user mail. Did not get anything relevant Thanks Rohit On Tuesday, June 19, 2012 7:20:27 PM UTC+5:30, benny.sadeh wrote: > your issue might be security-group related. > so first, just try allowing access to all, not just the security group on > ports 9200 & 9300. > if that solves the problem and you still want to restrict access, browse > the mailing list for related advice. > > Benny > > On Thursday, June 14, 2012 4:35:17 AM UTC-7, rohit reddy wrote: > > > Hi, > > > > I'm experimenting with Elasticsearch on AWS. I'm following the > > tutorial " > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/tutorials/2011/08/22/elasticsearch-on-ec2.html) > > ". > > > > I was able to successfully set up the elasticsearch instance on 1 > > Instance. But having problem setting it up of 2 instances. That is the 2 > > node is not able to discover the first node. > > Both are up independently but replication is not happening. > > > > I have used all the default configurations (5 shards and 1 replica) and > > just changed the following properties. I using local storage, did not > > configure s3 gateway > > > > cluster.name: iv-search > > > > cloud: > > aws: > > access\_key: > > secret\_key: > > discovery: > > type: ec2 > > cloud.aws.region: us-east-1 > > > > I have also opened 22, 9300 and 9200 ports. > > This is the my first time with both AWS and elasticsearch. So any help > > would be great. > > > > LOGS: > > > > [2012-06-14 07:07:14,798][INFO][node] [Xavin] > > {0.19.4}[2355]: started > > [2012-06-14 07:07:14,810][INFO][gateway] [Xavin] > > recovered [0] indices into cluster\_state > > [2012-06-14 09:40:18,845][INFO][node] [Zeus] > > {0.19.4}[2515]: initializing ... > > [2012-06-14 09:40:18,859][INFO][plugins] [Zeus] loaded > > [cloud-aws], sites > > [2012-06-14 09:40:20,236][DEBUG][discovery.zen.ping.multicast] [Zeus] > > using group [224.2.2.4], with port [54328], ttl [3], and address [null] > > [2012-06-14 09:40:20,239][DEBUG][discovery.zen.ping.unicast] [Zeus] using > > initial hosts , with concurrent\_connects [10] > > [2012-06-14 09:40:20,240][DEBUG][discovery.zen] [Zeus] using > > ping.timeout [3s] > > [2012-06-14 09:40:20,245][DEBUG][discovery.zen.elect] [Zeus] using > > minimum\_master\_nodes [-1] > > [2012-06-14 09:40:20,246][DEBUG][discovery.zen.fd] [Zeus] > > [master] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > > [2012-06-14 09:40:20,250][DEBUG][discovery.zen.fd] [Zeus] [node > > ] uses ping\_interval [1s], ping\_timeout [30s], ping\_retries [3] > > [2012-06-14 09:40:21,298][DEBUG][gateway.local] [Zeus] using > > initial\_shards [quorum], list\_timeout [30s] > > [2012-06-14 09:40:21,538][DEBUG][gateway.local.state.shards] [Zeus] took > > 0s to load started shards state > > [2012-06-14 09:40:21,540][DEBUG][gateway.local.state.meta] [Zeus] took > > 0s to load state > > [2012-06-14 09:40:21,603][INFO][node] [Zeus] > > {0.19.4}[2515]: initialized > > [2012-06-14 09:40:21,604][INFO][node] [Zeus] > > {0.19.4}[2515]: starting ... > > [2012-06-14 09:40:21,685][INFO][transport] [Zeus] > > bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/ > > 10.2.5.143:9300]} > > [2012-06-14 09:40:21,697][TRACE][discovery] [Zeus] > > waiting for 30s for the initial state to be set by the discovery > > [2012-06-14 09:40:21,725][TRACE][discovery.zen.ping.multicast] [Zeus] [1] > > sending ping request > > [2012-06-14 09:40:23,227][TRACE][discovery.zen.ping.multicast] [Zeus] [1] > > sending ping request > > [2012-06-14 09:40:24,729][DEBUG][discovery.zen] [Zeus] ping > > responses: {none} > > [2012-06-14 09:40:24,734][INFO][cluster.service] [Zeus] > > new\_master [Zeus][secret][inet[/10.2.5.143:9300]], reason: zen-disco-join > > (elected\_as\_master) > > [2012-06-14 09:40:24,801][TRACE][discovery] [Zeus] > > initial state set from discovery > > [2012-06-14 09:40:24,802][INFO][discovery] [Zeus] > > iv-search/ > > [2012-06-14 09:40:24,816][INFO][gateway] [Zeus] > > recovered [0] indices into cluster\_state > > [2012-06-14 09:40:24,818][INFO][http] [Zeus] > > bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/ > > 10.2.5.143:9200]} > > [2012-06-14 09:40:24,818][INFO][node] [Zeus] > > {0.19.4}[2515]: started > > > > Thanks > > Rohit ---
**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, 3:23am UTC](https://discuss.elastic.co/t/problem-with-cluster-setup-in-aws/8102/4 "2017-07-06T03:23:17Z")