For the second node, remove aws: access_key: xxxxxxxxxxxxxxxxxx secret_key: xxxxxxxxxxxxx region: us-west-2 discovery: type: ec2 ec2: tag: elasticsearch: true
It should work I think. Or set unicast to localhost and disable multicast -- David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 18 mars 2014 à 16:25:52, Bastien Chong (bastien...@gmail.com) a écrit: I'm not sure what I can change since I have the bare minimum config : The only difference between the 2 elasticsearch.yml config file are: node.master: false node.data: false path.conf: /etc/elasticsearchro path.data: /var/lib/elasticsearchro Both config share this part: cluster.name: ESCluster cloud: aws: access_key: xxxxxxxxxxxxxxxxxx secret_key: xxxxxxxxxxxxx region: us-west-2 discovery: type: ec2 ec2: tag: elasticsearch: true On Tuesday, March 18, 2014 11:00:15 AM UTC-4, David Pilato wrote: I think I understand what is happening here. Wondering if giving another elasticsearch.yml file as à configuration for the second node with all defaults (except cluster name) could help. -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 18 mars 2014 à 15:41, Bastien Chong <basti...@gmail.com> a écrit : Hi, I have a server with 2 ES instances. The first one is the master one, used to store documents. The second one is just there to receive requests from Kibana (I call it ES read-only), it has : node.master: false node.data: false Both are configured with cloud-aws plugin, and the http/java port are left by default for automatic assignment. When master start first, it's binded to 9200/9300, then the second one to 9201/9300. When I do : curl -XGET 'http://localhost:9200/_cluster/health?pretty=true' everything is working as expected and both nodes are in the same cluster. But, if I start the read-only instance first, discovery stop working. I have enabled DEBUG and TRACE but I didn't found what's the issue. I also tried to hardcode the port allocation : transport.tcp.port: 930(0/1) http.port: 920(0-1) And after that, It's actually worse, whatever the order I start the instances, EC2 discovery is broken. So it's sort of a race-condition that's happening. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8851834f-cefd-4732-8c34-f3410cec0c99%40googlegroups.com. For more options, visit 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/f31f79ec-ad39-440f-b2cd-36b642e18d48%40googlegroups.com. For more options, visit 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/etPan.5328835c.737b8ddc.97ca%40MacBook-Air-de-David.local. For more options, visit https://groups.google.com/d/optout.
