# ClusterBlockException after upgrade 1.7 to 2.1

**URL:** <https://discuss.elastic.co/t/clusterblockexception-after-upgrade-1-7-to-2-1/35579>\
**Category:** Elasticsearch\
**Created:** [November 25, 2015, 3:33pm UTC](https://discuss.elastic.co/t/clusterblockexception-after-upgrade-1-7-to-2-1/35579 "2015-11-25T15:33:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg\_5](https://avatars.discourse-cdn.com/v4/letter/g/f475e1/32.png) [@Greg\_5](https://discuss.elastic.co/u/Greg_5)\
**Post date:** [November 25, 2015, 3:33pm UTC](https://discuss.elastic.co/t/clusterblockexception-after-upgrade-1-7-to-2-1/35579/1 "2015-11-25T15:33:23Z")

</div>

Hello,

I upgraded my cluster from 1.7 to 2.1. Everything was green with the migration plugin.  
Some of my indices where set as read only.  
After the upgrade ALL my indices are not readable. I got a ClusterBlockException when a do a basic \_search request. Indices are OPEN.

Here is the config of the cluster and a index:

> <https://gist.github.com/anonymous/d6a8d80826e1e30612fd>

The only solution i have is to re-index everything but it's HUGE!

Any idea to solve this ?

---

<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:** [November 25, 2015, 7:03pm UTC](https://discuss.elastic.co/t/clusterblockexception-after-upgrade-1-7-to-2-1/35579/2 "2015-11-25T19:03:35Z")

</div>

Please post the full error message. Is the cluster still green?

---

<div class="post-metadata">

**Author:** ![Greg\_5](https://avatars.discourse-cdn.com/v4/letter/g/f475e1/32.png) [@Greg\_5](https://discuss.elastic.co/u/Greg_5)\
**Post date:** [November 25, 2015, 8:12pm UTC](https://discuss.elastic.co/t/clusterblockexception-after-upgrade-1-7-to-2-1/35579/3 "2015-11-25T20:12:49Z")

</div>

I retrieved the full message

{"error":{"root\_cause":[{"type":"cluster\_block\_exception","reason":"blocked by: [FORBIDDEN/5/index read (api)];"}],"type":"cluster\_block\_exception","reason":"blocked by: [FORBIDDEN/5/index read (api)];"},"status":403}

---

<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:** [November 26, 2015, 6:58am UTC](https://discuss.elastic.co/t/clusterblockexception-after-upgrade-1-7-to-2-1/35579/4 "2015-11-26T06:58:42Z")

</div>

Looks like the index is read only. You don't have index.blocks.read\_only set to true in the index settings have you?

---

<div class="post-metadata">

**Author:** ![Greg\_5](https://avatars.discourse-cdn.com/v4/letter/g/f475e1/32.png) [@Greg\_5](https://discuss.elastic.co/u/Greg_5)\
**Post date:** [November 26, 2015, 7:31am UTC](https://discuss.elastic.co/t/clusterblockexception-after-upgrade-1-7-to-2-1/35579/5 "2015-11-26T07:31:20Z")

</div>

I posted my index cluster settings and in both there is :

"blocks": {  
"read\_only": "false"  
}

But, even if the index is considered "read-only", it should be readable. In my case, i can't query (\_search) on it

---

<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, 11:35pm UTC](https://discuss.elastic.co/t/clusterblockexception-after-upgrade-1-7-to-2-1/35579/6 "2017-07-05T23:35:43Z")

</div>