I tried without luck. I changed : discovery.zen.ping.multicast.enabled: false > discovery.zen.ping.unicast.hosts: ["localhost"] > and commented the plugin part.
So by starting the 'read-only' instance first, it get 9200/9300. Then I start the master instance (9201/9301) In the Read-only log : > sending to [#zen_unicast_1#][inet[localhost/127.0.0.1:9300]] > It's not finding that I have an instance on port 9301. On Tuesday, March 18, 2014 2:07:38 PM UTC-4, David Pilato wrote: > > May be I was unclear. > > I know you need ec2 discovery. > > but you have two nodes per machine. > > Set the first one to use ec2 discovery and the second one to use regular > discovery. > > And could you open an issue in elasticsearch-cloud-aws plugin? > > > -- > *David Pilato* | *Technical Advocate* | *Elasticsearch.com* > @dadoonet <https://twitter.com/dadoonet> | > @elasticsearchfr<https://twitter.com/elasticsearchfr> > > > Le 18 mars 2014 à 19:03:04, Bastien Chong ([email protected]<javascript:>) > a écrit: > > What I didn't mention, is that this node won't be alone, there will be > about 6 other identical node, so I need the EC2 discovery feature. > > On Tuesday, March 18, 2014 1:33:16 PM UTC-4, David Pilato wrote: >> >> 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 <https://twitter.com/dadoonet> | >> @elasticsearchfr<https://twitter.com/elasticsearchfr> >> >> >> Le 18 mars 2014 à 16:25:52, Bastien Chong ([email protected]) 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 <[email protected]> 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' >>> <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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/8851834f-cefd-4732-8c34-f3410cec0c99%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/8851834f-cefd-4732-8c34-f3410cec0c99%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/f31f79ec-ad39-440f-b2cd-36b642e18d48%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/f31f79ec-ad39-440f-b2cd-36b642e18d48%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> 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 [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/bd4fb871-4113-418d-974c-6a7dd1f26975%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/bd4fb871-4113-418d-974c-6a7dd1f26975%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b389d676-df53-4bb6-9e54-fc939b4d6cac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
