# Elasticsearch configuration **URL:** \ **Category:** Elasticsearch\ **Created:** [October 12, 2021, 11:19am UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480 "2021-10-12T11:19:19Z")\ **Posts on this page:** 11\ **Page:** 2
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [October 12, 2021, 2:39pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/21 "2021-10-12T14:39:00Z")
Sorry due to limitation of number of characters I shared all the nodes logs separately ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [October 12, 2021, 2:58pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/22 "2021-10-12T14:58:51Z")
This one seems to be resolve now. ```auto curl -XGET 'orw-elkm1-vm:9200/_cat/nodes?v' ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name 10.102.86.119 1 60 1 0.30 0.23 0.14 m - orw-elkm2-vm 10.102.85.117 1 59 1 0.42 0.31 0.15 m * orw-elkm1-vm 10.102.85.245 26 9 1 0.30 0.21 0.11 di - orw-elkd1-vm ``` ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [October 12, 2021, 3:00pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/23 "2021-10-12T15:00:06Z")
I stopped the service on all nodes and wiped the lib directory. rm -rf /var/lib/Elasticsearch/\* Thanks you all for all your support. Thanks Niraj ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [October 12, 2021, 3:02pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/24 "2021-10-12T15:02:01Z")
> [@niraj\_pandey](#): > > I stopped the service on all nodes and wiped the lib directory. This helped because this was your issue: > Caused by: org.elasticsearch.cluster.coordination.CoordinationStateRejectedException: join validation on cluster state with a different cluster uuid Bp1EZ69WSFq8IR4DFe8nUw than local cluster uuid WwcRVF99Qmu4J2azujyM9g, rejecting It seems that your nodes have joined a previous cluster before for some reason, deleting the data directory of the nodes, as you did, would wipe out this information and allow them to join a new cluster. ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [October 12, 2021, 3:05pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/25 "2021-10-12T15:05:12Z")
Just want to confirm 2 things. 1- I have two master nodes so in case 1 goes down the cluster would be up and running , right ? 2- I have 3 data nodes so if 1 goes down we can survive without any data lose , correct ? ---
**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\ **Post date:** [October 12, 2021, 3:16pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/26 "2021-10-12T15:16:22Z")
Correct, make sure you have primary indices with at least 1 replica. ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [October 12, 2021, 3:27pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/27 "2021-10-12T15:27:05Z")
Is there any specific way to achieve this ? ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [October 12, 2021, 3:29pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/28 "2021-10-12T15:29:34Z")
> [@niraj\_pandey](#): > > I have two master nodes so in case 1 goes down the cluster would be up and running , right ? No, you need 3 master nodes for high availability, with just 2 master nodes if one of them goes down, your entire cluster will not work. Read this part of the [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/high-availability-cluster-design.html#high-availability-cluster-design) about cluster resilience and also [this one](https://www.elastic.co/guide/en/elasticsearch/reference/current/high-availability-cluster-small-clusters.html#high-availability-cluster-small-clusters) about resilience in small cluster. WIth 2 nodes you do not have resilience to failure, you will need 3 master nodes or at least 1 tie-break node as explained in the documentation. Also, you have 2 master nodes and just 1 data node, you cannot lose any master and you can also not lose the data node, you can also not use replicas as you only have 1 data node. The best way in this case would be to have all your 3 nodes working as both master anda data nodes. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 13, 2021, 12:22am UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/29 "2021-10-13T00:22:20Z")
> [@niraj\_pandey](#): > > I am trying to configure Elasticsearch 7.0.0 Please don't. 7.0 is very well past [EOL](https://www.elastic.co/support/eol), 7.15 is latest and you should be using that. > [@niraj\_pandey](#): > > ```auto > network.host: 10.102.85.117 > http.host: 0.0.0.0 > http.port: 9200 > > ``` This doesn't make a lot of sense. Just set `network.host` and all of the rest will be inherited from that. ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [October 16, 2021, 4:31am UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/30 "2021-10-16T04:31:14Z")
Thank you all for your support. Cluster is up now. curl -X GET "rw-elkd1-vm:9200/\_cluster/health?pretty" ```auto { "cluster_name" : "elk-cluster", "status" : "green", "timed_out" : false, "number_of_nodes" : 5, "number_of_data_nodes" : 3, "active_primary_shards" : 15, "active_shards" : 30, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 0, "active_shards_percent_as_number" : 100.0 } ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 13, 2021, 4:31am UTC](https://discuss.elastic.co/t/elasticsearch-configuration/286480/31 "2021-11-13T04:31:31Z")
Closed on November 13, 2021, 4:31am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. [Previous page](https://discuss.elastic.co/t/elasticsearch-configuration/286480.md?page=1)