Cluster failing after changing path.data in elasticsearch.yml


(Max Kimoby) #1

ES 6.4

I recently changed my path.data on some nodes to point to mounted volume disk space. This is the only config I changed and since then my cluster fails to start. This is the error I get from logs when running curl -X GET "localhost:9200/_cluster/health":

{"error":{"root_cause":[{"type":"master_not_discovered_exception","reason":null}],"type":"master_not_discovered_exception","reason":null},"status":503}

I've read probably every article on the subject. I currently have 6 nodes with 4 master nodes (1 is set to data:false). I haven't had any problems with these configs. I proceeded to delete all my indices, and manually deleted the data.

Minimum master nodes :

discovery.zen.minimum_master_nodes: 4

I've tried pinging all my hosts list and all of them are actually pinging!

New path.data :

path.data: /mnt/elasticsearch_4_volume/elasticsearch

ES is correctly started on every node:

{ "name" : "elasticsearch-1", "cluster_name" : "diligent-courteous-wolf", "cluster_uuid" : "_na_", "version" : { "number" : "6.4.0", "build_flavor" : "default", "build_type" : "deb", "build_hash" : "595516e", "build_date" : "2018-08-17T23:18:47.308994Z", "build_snapshot" : false, "lucene_version" : "7.4.0", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You Know, for Search" }

Can anyone give my a hand on this please?


(system) #2

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