# Zend discovery feature of es to avoid split brain problem and heap memory usage of ES

**URL:** <https://discuss.elastic.co/t/zend-discovery-feature-of-es-to-avoid-split-brain-problem-and-heap-memory-usage-of-es/22584>\
**Category:** Elasticsearch\
**Created:** [March 9, 2015, 2:59pm UTC](https://discuss.elastic.co/t/zend-discovery-feature-of-es-to-avoid-split-brain-problem-and-heap-memory-usage-of-es/22584 "2015-03-09T14:59:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Phani\_Nadiminti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phani_nadiminti/32/45381_2.png) [@Phani\_Nadiminti](https://discuss.elastic.co/u/Phani_Nadiminti)\
**Post date:** [March 9, 2015, 2:59pm UTC](https://discuss.elastic.co/t/zend-discovery-feature-of-es-to-avoid-split-brain-problem-and-heap-memory-usage-of-es/22584/1 "2015-03-09T14:59:57Z")

</div>

Hi All,

I have few doubts in es,how es managing heap memory.

```
 my cluster have following configurations all three nodes are master 

```

and data eligible in my cluster

```
  node 1 : 12 GB Heap total RAM : 24 GB
  node 2 : 12 GB Heap total RAM : 24 GB
  node 3 : 12 GB Heap total RAM : 24 GB

      I have an idea how elasticsearch will serve requests by sending 

```

requests to all nodes in a cluster but now my question is how elasticsearch  
will manage heap space when serving requests. is it manage, load by using  
heap space from all three servers ? How it will manage heap space  
efficiently.

```
      and 

       to avoid split brain i need to add following properties to 

```

elasticsearch.yml file.

```
              discovery.zen.minimum_master_nodes : 2
              discovery.zen.ping.timeout: 3 

         All three nodes in my cluster master and data eligible so is 

```

it required to add the above properties in all three nodes(in  
elasticsearch.yml file ) in my cluster?

```
         please help me in this concepts.

```

Thanks  
phani

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/74119a88-1d12-4448-bf88-df9066c42fbc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/74119a88-1d12-4448-bf88-df9066c42fbc%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:27am UTC](https://discuss.elastic.co/t/zend-discovery-feature-of-es-to-avoid-split-brain-problem-and-heap-memory-usage-of-es/22584/2 "2017-07-06T00:27:46Z")

</div>