# How to fix Unstable Clustering of elastic search!

**URL:** <https://discuss.elastic.co/t/how-to-fix-unstable-clustering-of-elastic-search/65286>\
**Category:** Elasticsearch\
**Created:** [November 7, 2016, 10:34pm UTC](https://discuss.elastic.co/t/how-to-fix-unstable-clustering-of-elastic-search/65286 "2016-11-07T22:34:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brett1](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@Brett1](https://discuss.elastic.co/u/Brett1)\
**Post date:** [November 7, 2016, 10:34pm UTC](https://discuss.elastic.co/t/how-to-fix-unstable-clustering-of-elastic-search/65286/1 "2016-11-07T22:34:12Z")

</div>

Hi!  
We are now using ES version 1.7.3  
Recently we have founded one problem with this Ver.1.7.3 ,  
The problem is about unstable clustering operations. This is not frequent failure but rarely happens especially when we shut down by CLI command while ES is collecting Data, after rebooting then cluster is broken. (OS is on Linux Ubuntu 12.04, HW is composed of one Master node and two data nodes,  
This is not Hadoop DB but just locally distributed clusters)  
This is tough explanation about the failure but please help me out with any tips and informations!  
I don’t know why the reason is and don’t know how it can be fixed? Is this happened because of using still low E/S version?) Is there anybody who experienced same situation?  
This can cause big problem sometimes for my customer.  
Please tell me any helpful tips!

Hope answers!

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [November 7, 2016, 10:53pm UTC](https://discuss.elastic.co/t/how-to-fix-unstable-clustering-of-elastic-search/65286/2 "2016-11-07T22:53:54Z")

</div>

You obviously selected to use only one master node.

So you are fully responsible for your cluster failures.

---

<div class="post-metadata">

**Author:** ![Brett1](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@Brett1](https://discuss.elastic.co/u/Brett1)\
**Post date:** [November 8, 2016, 2:49am UTC](https://discuss.elastic.co/t/how-to-fix-unstable-clustering-of-elastic-search/65286/3 "2016-11-08T02:49:35Z")

</div>

Dear Jorg Prante!  
Thank you your comments!  
I'll check the problem and construct more master Node!  
then let's talk again!  
Thank you very much!

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 8, 2016, 6:22am UTC](https://discuss.elastic.co/t/how-to-fix-unstable-clustering-of-elastic-search/65286/4 "2016-11-08T06:22:41Z")

</div>

Make you 2 data nodes master eligible or add another 2 dedicates master nodes. You basically always want to have 3 master eligible nodes so that the remaining 2 can form a majority of one goes down. Also remember to set `minimum_master_nodes` to 2 when you have 3 master eligible nodes in order to avoid split-brain scenarios.

---

<div class="post-metadata">

**Author:** ![Brett1](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@Brett1](https://discuss.elastic.co/u/Brett1)\
**Post date:** [November 9, 2016, 5:51am UTC](https://discuss.elastic.co/t/how-to-fix-unstable-clustering-of-elastic-search/65286/5 "2016-11-09T05:51:46Z")

</div>

Dear Chritian\_Dahlqvist,

Thanks for helping me out!

I’ll check that out!

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 7, 2016, 5:51am UTC](https://discuss.elastic.co/t/how-to-fix-unstable-clustering-of-elastic-search/65286/6 "2016-12-07T05:51:53Z")

</div>

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