You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just got this now, and from what I see it is not in any way fatal as such, but to me it smells like there might be an issue either in ES itself, or in the discovery logic:
Note the first "failed to send join request" in Node2's logs: the timing is awfully close to when the master actually says its a master. Times should be comparable, both nodes run ntp.
This is with elasticsearch-cloud-aws 2.7.0.
The text was updated successfully, but these errors were encountered:
Note though that the issue in this ticket isn't a problem as such, elasticsearch worked out the cluster configuration after all. It's mainly that there is a chance that something either in the cloud-aws or the core elasticsearch code does operations in the wrong order.
do you have solve it? we have a problem ,and i dont know how to solve it, can you help me ? We have to put a plugin to the produce envrionment, but when we stop a node, the log produce a error: "TransportService is closed stopped can't send request", and when we restart the node,it's a long time even 1 minute util cluster find the node, we don't know how to do we use AWS plugin elasticsearch 1.5.2
the conffig is :
discovery.type: "ec2"
discovery.ec2.host_type: "private_ip"
discovery.ec2.ping_timeout: "30s"
if discovery.ec2.ping_timeout is short, cluster can't build
Just got this now, and from what I see it is not in any way fatal as such, but to me it smells like there might be an issue either in ES itself, or in the discovery logic:
Node1:
Node2:
Note the first "failed to send join request" in Node2's logs: the timing is awfully close to when the master actually says its a master. Times should be comparable, both nodes run ntp.
This is with elasticsearch-cloud-aws 2.7.0.
The text was updated successfully, but these errors were encountered: