Hi there, I've been struggling for a few days to get a basic cluster going using AWS OpsWorks using the new plugin. Admitedly I'm pretty new to the Idea of Chef/AWS, but I have setup a private cluster using Puppet so I'm not a complete newbie to Elasticsearch.
Nodes have installed, have started, I can access port 9200 on each, but they don't find each other using the EC2 API (status: 503) and hence don't form a cluster like they do in a normal environment. Is anyone able to spot what I may be doing wrong, or simply provide their chef cookbooks and JSON config for using Elasticsearch > v1.0? *Config* The following is how I've configured everything currently, happy to provide any further details. I've based my config on this AWS blog post http://blogs.aws.amazon.com/application-management/post/Tx3MEVKS0A4G7R5/Deploying-Elasticsearch-with-OpsWorks I have a git repo with a bunch of submodules hosting my cookbooks https://github.com/stuart-warren/opsworks-cookbooks My stack is called "elasticsearch-test" It's set to use the eu-west-1 region (Ireland) Using Chef 11.4 My Layer is called ES-Search-Test My custom chef recipes: Setup - java::default Deploy - elasticsearch elasticsearch::aws elasticsearch::nginx I have 2 instances in the same availability zone I have an App: elasticsearch Same git repo url And a deployment with this Custom Chef JSON http://pastebin.com/P6vdWBGL *Observations* Each node gets the tag "opsworks:stack=elasticsearch-test" so that is what I'm using as a filter Each node can telnet to the others 9300 port so I don't think it is a Security groups/communications issue Each node can run `aws ec2 describe-instances --filters Name=tag:opsworks:stack,Values=elasticsearch-test` without specifying keys and get the nodes, so I don't think it is a profiles/API issue. Nginx does not yet work either, but that is a secondary priority at the moment. *Config* Here is the generated config from one of the nodes http://pastebin.com/QNEKrf9N *Logs* This is my log after a restart [2014-04-04 10:19:32,552][INFO ][node ] [amefurikozo.localdomain] version[1.1.0], pid[3349], build[2181e11/2014-03-25T15:59:51Z] [2014-04-04 10:19:32,552][INFO ][node ] [amefurikozo.localdomain] initializing ... [2014-04-04 10:19:32,631][INFO ][plugins ] [amefurikozo.localdomain] loaded [cloud-aws], sites [] [2014-04-04 10:19:38,683][INFO ][node ] [amefurikozo.localdomain] initialized [2014-04-04 10:19:38,683][INFO ][node ] [amefurikozo.localdomain] starting ... [2014-04-04 10:19:38,805][INFO ][transport ] [amefurikozo.localdomain] bound_address {inet[/0.0.0.0:9300]}, publish_address {inet[/172.31.x.x:9300]} [2014-04-04 10:20:08,853][WARN ][discovery ] [amefurikozo.localdomain] waited for 30s and no initial state was set by the discovery [2014-04-04 10:20:08,853][INFO ][discovery ] [amefurikozo.localdomain] elasticsearch-test-dsi/z2CyXhZnTuWVTuD_07v5lQ [2014-04-04 10:20:08,863][INFO ][http ] [amefurikozo.localdomain] bound_address {inet[/0.0.0.0:9200]}, publish_address {inet[/172.31.x.x:9200]} [2014-04-04 10:20:08,961][INFO ][node ] [amefurikozo.localdomain] started -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/48dfb888-9e61-42d6-982b-b76feaa795cd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
