* Matt Dainty <[email protected]> [2014-04-11 11:01:33]:
>
> 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.]
I ran out of time to poke at this over the weekend so I left it running,
however I've resumed looking at it and now it's also logging this:
[2014-04-14 10:21:12,706][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.transport.RemoteTransportException:
[es-master-02][inet[/172.31.x.x:9300]][discovery/zen/join];
java.lang.OutOfMemoryError: unable to create new native thread]
So leaving the tribe node attempting to join the cluster has caused it
to exhaust its heap somehow. Anything I can grab from this to see what's
happened?
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/20140414092423.GA15419%40simulant.bodgit-n-scarper.com.
For more options, visit https://groups.google.com/d/optout.
