# Master Node behaviour

**URL:** <https://discuss.elastic.co/t/master-node-behaviour/62233>\
**Category:** Elasticsearch\
**Created:** [October 5, 2016, 5:11am UTC](https://discuss.elastic.co/t/master-node-behaviour/62233 "2016-10-05T05:11:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shivkumar](https://avatars.discourse-cdn.com/v4/letter/s/8797f3/32.png) [@shivkumar](https://discuss.elastic.co/u/shivkumar)\
**Post date:** [October 5, 2016, 5:11am UTC](https://discuss.elastic.co/t/master-node-behaviour/62233/1 "2016-10-05T05:11:19Z")

</div>

Hello,

Yesterday my cluster changed its status to RED. My Master node EC2 instance was having 8GB of EBS volume.

I did not able to find the reason behind the cluster status changing to RED. Then I tried to add another data node to my cluster, still the status did not changed to healthy.

Then I increased the volume size of my master node, then the cluster turned to GREEN .

I am not able to understand why this happened.

The point I am concerned about is .

1. If it was issue regarding to space then why the cluster did not changed its status when I added the third data node.
2. If after increasing the EBS size of master node , my cluster becomes health , does my data for the indices stored on Master node.

For further investigation I took a look at my Master node inside data/indices I found some data with [indices.So](http://indices.So) I am not able to understand does my data is stored on master node also.

my Master Node has the following configuration 🙂  
node.master: true  
node.data: flase

I want to understand the reason and cause of this behavior and other things around it.  
I hope I am clear with my question.

Thank you

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [October 5, 2016, 5:36am UTC](https://discuss.elastic.co/t/master-node-behaviour/62233/2 "2016-10-05T05:36:40Z")

</div>

Have you looked for clues about what happened in the Elasticsearch logs?

---

<div class="post-metadata">

**Author:** ![shivkumar](https://avatars.discourse-cdn.com/v4/letter/s/8797f3/32.png) [@shivkumar](https://discuss.elastic.co/u/shivkumar)\
**Post date:** [October 5, 2016, 6:23am UTC](https://discuss.elastic.co/t/master-node-behaviour/62233/3 "2016-10-05T06:23:56Z")

</div>

Not yet sir let me check once.  
I will get you back after going through logs.  
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:** [July 5, 2017, 10:14pm UTC](https://discuss.elastic.co/t/master-node-behaviour/62233/4 "2017-07-05T22:14:56Z")

</div>