No nodes will join cluster

Elastic Stack Elasticsearch
1

Hey there.

I'm creating a 2 node cluster with es on two ec2 servers, but the nodes
won't join in the same cluster... The servers/nodes discover, add each
other, and then disconnect without ever joining the same cluster. (i had no
problem setting up es on a single server.)

Here is the elasticsearch.yml i have...

cluster.name: es-cluster
cloud:
aws:
access_key: OUR_ACCESS_KEY
secret_key: OUR_SECRET_KEY
region: us-east-1
node.name: es-cluster-node-1
discovery:

type: ec2

If i have the s3 bucket configured, they'll grab whatever's there and do
some gateway communications, but still end up each as the only node in
their own cluster of the same name.

Also, I can telnet from one to the other on ports 9200-9300 manually.

Thoughts? Anything else I should include here?

Thanks!
Sadie

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

2

ok. if i comment out ec2 discovery and specify the hosts then they see each
other and both join the same cluster.

discovery.zen.ping.unicast.hosts:
["logstore2.example.com:9300","logstore.example.com:9300"]

but i still need to get them talking dynamically via discovery.

thoughts?

On Wednesday, May 15, 2013 5:29:14 PM UTC-7, Sadie C wrote:

Hey there.

I'm creating a 2 node cluster with es on two ec2 servers, but the nodes
won't join in the same cluster... The servers/nodes discover, add each
other, and then disconnect without ever joining the same cluster. (i had no
problem setting up es on a single server.)

Here is the elasticsearch.yml i have...

cluster.name: es-cluster
cloud:
aws:
access_key: OUR_ACCESS_KEY
secret_key: OUR_SECRET_KEY
region: us-east-1
node.name: es-cluster-node-1
discovery:

type: ec2

If i have the s3 bucket configured, they'll grab whatever's there and do
some gateway communications, but still end up each as the only node in
their own cluster of the same name.

Also, I can telnet from one to the other on ports 9200-9300 manually.

Thoughts? Anything else I should include here?

Thanks!
Sadie

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

3

ok. i figured it out.

i needed to set discovery.ec2.groups in the elasticsearch.yml file --

discovery.ec2.groups: ["My Security Group Name"]

i think that the nodes were finding so many other servers in the
discovery process and timing out before getting a chance to communicate
with the other actual nodes for this cluster. i'm not sure this is what
happening because from the log it looked like it disconnected from many of
the servers it found (including the node it should have chatted with), then
timed out trying to connect to a few irrelevant other servers it found in
discovery, and then continued to disconnect from the rest. i can't tell
just from looking at the log whether it timed out trying to connect to the
other node or timed out from the overall process or what...

but anyhoo... they're talking. so yay.

On Wednesday, May 15, 2013 8:58:53 PM UTC-7, Sadie C wrote:

ok. if i comment out ec2 discovery and specify the hosts then they see
each other and both join the same cluster.

discovery.zen.ping.unicast.hosts: ["logstore2.example.com:9300","
logstore.example.com:9300"]

but i still need to get them talking dynamically via discovery.

thoughts?

On Wednesday, May 15, 2013 5:29:14 PM UTC-7, Sadie C wrote:

Hey there.

I'm creating a 2 node cluster with es on two ec2 servers, but the nodes
won't join in the same cluster... The servers/nodes discover, add each
other, and then disconnect without ever joining the same cluster. (i had no
problem setting up es on a single server.)

Here is the elasticsearch.yml i have...

cluster.name: es-cluster
cloud:
aws:
access_key: OUR_ACCESS_KEY
secret_key: OUR_SECRET_KEY
region: us-east-1
node.name: es-cluster-node-1
discovery:

type: ec2

If i have the s3 bucket configured, they'll grab whatever's there and do
some gateway communications, but still end up each as the only node in
their own cluster of the same name.

Also, I can telnet from one to the other on ports 9200-9300 manually.

Thoughts? Anything else I should include here?

Thanks!
Sadie

--
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.
For more options, visit https://groups.google.com/groups/opt_out.