* David Pilato <[email protected]> [2014-04-11 08:06:28]:
>
> Could you try using _ec2:publicIp_ and see how it goes?
Ok, I can get the cluster to associate when using _ec2:publicIp_ however
EC2 security groups don't work very well; I have to add the public IP
address of every node in the cluster to the inbound rules of the
security group that they're all in otherwise they can't connect to each
other. Whereas before I just had a rule that said any traffic is allowed
if it's from the same security group.
I'd much rather get it working keeping the cluster traffic using the
private IP addresses.
With the cluster up I tried the tribe node again, now it just logs this
every 20 seconds:
[2014-04-11 15:38:25,497][INFO ][discovery.zen ]
[es-tribe-01/sydney] failed to send join request to master
[[es-master-02][Vii7h7O1RNy6rpGPRXVDLQ][es-master-02][inet[/54.206.x.x:9300]]{aws_availability_zone=ap-southeast-2b,
data=false, master=true}], reason
[org.elasticsearch.ElasticsearchTimeoutException: Timeout waiting for task.]
What timeout is that referring to?
I can telnet to the TCP ports on the master node and running tcpdump on
each node I can see traffic going back and forth so it is connected. The
master nodes are not logging anything while this is happening, I just
get:
[2014-04-11
15:59:02,219][DEBUG][org.apache.http.impl.conn.PoolingClientConnectionManager]
Closing connections idle longer than 60 SECONDS
once a minute.
I've tried setting discovery.zen.ping_timeout to 10s but it doesn't help.
All the other timeouts I can find seem to default to 30s which is more
than enough.
Matt
--
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/20140411150129.GD2245%40simulant.bodgit-n-scarper.com.
For more options, visit https://groups.google.com/d/optout.
