# ClusterBlockException issue

**URL:** <https://discuss.elastic.co/t/clusterblockexception-issue/80477>\
**Category:** Elasticsearch\
**Created:** [March 29, 2017, 12:24pm UTC](https://discuss.elastic.co/t/clusterblockexception-issue/80477 "2017-03-29T12:24:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balamurali](https://avatars.discourse-cdn.com/v4/letter/b/90db22/32.png) [@Balamurali](https://discuss.elastic.co/u/Balamurali)\
**Post date:** [March 29, 2017, 12:24pm UTC](https://discuss.elastic.co/t/clusterblockexception-issue/80477/1 "2017-03-29T12:24:40Z")

</div>

Hi All,

We are using elasticsearch 1.3.7 cluster with 5 data only nodes and 3 master only nodes with 6 GB heap size for each node.  
FYI,already we are in ES upgrading progress.

Today suddenly one node got removed , shards are gone to unassigned .  
Data node got removed due to GC occurrence and Slow queries  
**Why we are getting this ClusterBlockException in data node failure?**

We gone to cluster with master only and Data only nodes for avoid this ClusterBlockException because we already suffered this issue when master node (data cum master) failure occurs .

**can you please help and suggest us!!**

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 29, 2017, 12:40pm UTC](https://discuss.elastic.co/t/clusterblockexception-issue/80477/2 "2017-03-29T12:40:00Z")

</div>

Upgrade ASAP!

At least to latest 1.7 although 1.7 is not maintained anymore (EOL).

> [@Balamurali](#):
>
> We gone to cluster with master only and Data only nodes for avoid this ClusterBlockException because we already suffered this issue when master node (data cum master) failure occurs .

That was a good idea indeed. I'd recommend keeping that strategy.

May be restart the master nodes? At least look at their logs.

---

<div class="post-metadata">

**Author:** ![Balamurali](https://avatars.discourse-cdn.com/v4/letter/b/90db22/32.png) [@Balamurali](https://discuss.elastic.co/u/Balamurali)\
**Post date:** [March 29, 2017, 1:08pm UTC](https://discuss.elastic.co/t/clusterblockexception-issue/80477/3 "2017-03-29T13:08:36Z")

</div>

Thanks @dadoonet

> [@dadoonet](#):
>
> May be restart the master nodes? At least look at their logs.

Checked in master logs . there is no restart in master nodes.

while checking log , master node removed data node from cluster due to long pause GC .  
after GC end, data node back to normal ( not in cluster ) and that data node starts electing new master .  
it is added to cluster after bouncing that node

then what is reason behind ClusterBlockException issue ?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 29, 2017, 1:32pm UTC](https://discuss.elastic.co/t/clusterblockexception-issue/80477/4 "2017-03-29T13:32:02Z")

</div>

So may be try to restart the master nodes?

---

<div class="post-metadata">

**Author:** ![Balamurali](https://avatars.discourse-cdn.com/v4/letter/b/90db22/32.png) [@Balamurali](https://discuss.elastic.co/u/Balamurali)\
**Post date:** [March 29, 2017, 2:11pm UTC](https://discuss.elastic.co/t/clusterblockexception-issue/80477/5 "2017-03-29T14:11:16Z")

</div>

@dadoonet Thanks lot

---

<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:** [April 26, 2017, 2:11pm UTC](https://discuss.elastic.co/t/clusterblockexception-issue/80477/6 "2017-04-26T14:11:46Z")

</div>

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