I just ran a small test on a ec2 instance. I just set
node.master: true node.data: false on a node without and then with cloud-aws-plugin and it worked well in both cases. Could you try to simplify your settings to see what setting is actually causing this? cluster.name: testingelastic cloud.aws.access_key: <ACCESS_KEY> cloud.aws.secret_key: <SECRET_KEY> discovery.type: ec2 node.master: true node.data: false -- David Pilato - Developer | Evangelist elastic.co @dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr <https://twitter.com/elasticsearchfr> | @scrutmydocs <https://twitter.com/scrutmydocs> > Le 22 avr. 2015 à 13:33, Zaid Amir <redserpe...@gmail.com> a écrit : > > Both nodes have: > > ElasticSearch: 1.5.0 > Cloud-AWS: 2.5.0 > > On Wednesday, April 22, 2015 at 2:29:39 PM UTC+3, David Pilato wrote: > Which versions for: > > Elasticsearch > Cloud-aws-plugin > > ? > > -- > David ;-) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 22 avr. 2015 à 12:41, Zaid Amir <redse...@gmail.com <javascript:>> a écrit > : > >> Hi, >> >> I am starting a new cluster and I want it to be set with two nodes. One is a >> data only node and the other is a master only node. Both nodes are hosted on >> Amazon EC2 and are in the same region >> >> Here is my configuration for both nodes. >> >> Master Node: >> >> cluster.name <http://cluster.name/>: testingelastic >> cloud.aws.access_key: <ACCESS_KEY> >> cloud.aws.secret_key: <SECRET_KEY> >> cloud.aws.protocol: http >> discovery.type: ec2 >> discovery.ec2.tag.Search: Elastic >> discovery.ec2.ping_timeout: 90s >> discovery.zen.ping.multicast.enabled: false >> node.name <http://node.name/>: "node_m" >> node.master: true >> node.data: false >> index.number_of_shards: 1 >> index.number_of_replicas: 1 >> network.publish_host: <STATIC_IP_ADDRESS> >> http.enabled: true >> http.cors.enables: true >> http.cors.allow-origin: "*" >> discovery.zen.ping.timeout: 600s >> >> >> Data Node: >> >> cluster.name <http://cluster.name/>: testingelastic >> cloud.aws.access_key: <ACCESS_KEY> >> cloud.aws.secret_key: <SECRET_KEY> >> cloud.aws.protocol: http >> discovery.type: ec2 >> discovery.ec2.tag.Search: Elastic >> discovery.ec2.ping_timeout: 90s >> discovery.zen.ping.multicast.enabled: false >> node.name <http://node.name/>: "node_d" >> path.data: /elasticdata/data/ >> node.master: false >> node.data: true >> index.number_of_shards: 1 >> index.number_of_replicas: 1 >> network.publish_host: <STATIC_IP_ADDRESS> >> http.enabled: true >> http.cors.enables: true >> http.cors.allow-origin: "*" >> iscovery.zen.ping.timeout: 600s >> >> >> Now when I start the elasticsearch service on the Master Node, the service >> starts fine with now errors in the logs. Yet it keeps giving me a 503 >> whenever I try to connect to it. >> >> Calling: curl -XGET localhost:9200/_stats on the master node gives the >> following exception: >> >> { >> "error": "ClusterBlockException[blocked by: [SERVICE_UNAVAILABLE/1/state not >> recovered / initialized];[SERVICE_UNAVAILABLE/2/no master];]","status":503 >> } >> >> So it seems for some weird reason that it does not elect itself as a master >> node. >> >> >> When checking the logs on the data node, it seems that it is able to detect >> the master node yet cannot connect to it with the following error in the >> logs: >> >> [2015-04-22 10:38:03,604][INFO ][discovery.ec2 ] [node_d] failed >> to send join request to master [[node_m][<ID>][<IP>][inet[<IP>]]{data=false, >> master=t$ >> >> I removed the IP addresses for security but I assure you they are correct. >> >> So what is going on here, and why is my master node failing to see itself as >> a master node? >> >> >> >> >> >> >> >> -- >> 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 <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/c5466db8-f614-4d52-a245-bd361b6953ad%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/c5466db8-f614-4d52-a245-bd361b6953ad%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscr...@googlegroups.com > <mailto:elasticsearch+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/30ee9166-5590-434b-8fc2-d8b1196e4650%40googlegroups.com > > <https://groups.google.com/d/msgid/elasticsearch/30ee9166-5590-434b-8fc2-d8b1196e4650%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/862D11C0-116C-48ED-8948-AE99A25B0520%40pilato.fr. For more options, visit https://groups.google.com/d/optout.
