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 | @elasticsearchfr
Le 18 mars 2014 à 19:03:04, Bastien Chong (bastien974@gmail.com) 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 | @elasticsearchfr
Le 18 mars 2014 à 16:25:52, Bastien Chong (basti...@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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/bd4fb871-4113-418d-974c-6a7dd1f26975%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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/etPan.53288b6b.153ea438.97ca%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.
