Elasticsearch data dependency

in the case of capturing the elastic volume as the host volume in the Kubernetes environment, there is a problem that the node does not work properly when the node position changes when all Elasticsearch PODs are lowered and raised.

In other words, the Elasitc POD using the host volume running on node 1 is created on node 2.

Can you see why this is like this ??

When elastic stores data, does it store its node name as well ?? The new POD will not remember what data it had and what it was .. It's strange ..

You need to use persistent volumes for the Elasticsearch data directories as these hold the data as well as the cluster state, which is required across restarts.

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.