I have a Elasticsearch 5.5 cluster consists of 8 nodes (all the same config of both master and data nodes) and each node contains about 60 shards and each shard contains about 15GB data.
I run into the problem that if I restart one node, when the node rejoined the cluster, the data in that node is suddenly all gone and the cluster then started relocating shards to this node as if this is a new node, and the process took many hours to complete.
I tried to flush sync before the restart, but the problem persists. the flush sync api call is not full success because one index is accepting writing operation all the time.
I don't think it is the normal behavior when a node restart, but I don't know where I did wrong, any idea?
Elasticsearch 5.5 is EOL and no longer supported. Please upgrade ASAP.
(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns )
5.X is super old, and it never handled recoveries from restarts very gracefully. This sort of behaviour is pretty common as a result.
oh, that's sad to hear..
can you suggest a version that "handle recoveries from restarts very gracefully" ? will v6.8 suffice?
I hope to keep the changes as minimal as possible to my working application
Anything prior to 7.10 is EOL as well, so there's no support for them.
6.X was better, but it's still EOL.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.