# Issue with elastic cluster after upgrade to 6.5.0

**URL:** <https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768>\
**Category:** Elasticsearch\
**Created:** [November 21, 2018, 6:34pm UTC](https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768 "2018-11-21T18:34:06Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![planetvortex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/planetvortex/32/31080_2.png) [@planetvortex](https://discuss.elastic.co/u/planetvortex)\
**Post date:** [November 21, 2018, 6:34pm UTC](https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768/1 "2018-11-21T18:34:07Z")

</div>

My master node is reporting the following error "role retrieval failed from [native roles store]"

> [2018-11-21T18:27:50,739][WARN][o.e.x.s.a.s.CompositeRolesStore] [[elk-master-2.mydomain.net](http://elk-master-2.mydomain.net)] role retrieval failed from [native roles store]  
> org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];

I can no longer view roles, i can list them, but not view the individual contents of any of the roles, nor can I create users.  
I've tried my own account, and have tried the elastic user. The upgrade may not be the issue.  
I'm not sure what to provide to you.

---

<div class="post-metadata">

**Author:** ![planetvortex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/planetvortex/32/31080_2.png) [@planetvortex](https://discuss.elastic.co/u/planetvortex)\
**Post date:** [November 21, 2018, 7:26pm UTC](https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768/2 "2018-11-21T19:26:15Z")

</div>

OK, so this may be the wrong way to handle things.

```
PUT .*/_settings
{
"index": {
"blocks": {
"read_only_allow_delete": "false"
}
}
}

PUT */_settings
{
"index": {
"blocks": {
"read_only_allow_delete": "false"
}
}
}
```

---

<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 21, 2018, 7:28pm UTC](https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768/3 "2018-11-21T19:28:34Z")

</div>

That error message sometimes indicates that you are running out of disk space and have exceeded the flood stage watermark (defaults to 95% full). If that is the case, you will need to free up space as indices otherwise will go back to read-only mode.

---

<div class="post-metadata">

**Author:** ![planetvortex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/planetvortex/32/31080_2.png) [@planetvortex](https://discuss.elastic.co/u/planetvortex)\
**Post date:** [November 21, 2018, 7:35pm UTC](https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768/4 "2018-11-21T19:35:47Z")

</div>

I WAS having an issue with the space, which I resolved, and the error never cleared itself. Of course by the time I cleared things up, the monitoring wouldn't run anymore.

---

<div class="post-metadata">

**Author:** ![planetvortex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/planetvortex/32/31080_2.png) [@planetvortex](https://discuss.elastic.co/u/planetvortex)\
**Post date:** [November 21, 2018, 7:47pm UTC](https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768/5 "2018-11-21T19:47:56Z")

</div>

How long should it take to become NOT read-only after a space issue has been cleared?

---

<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 21, 2018, 8:00pm UTC](https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768/6 "2018-11-21T20:00:40Z")

</div>

I believe you need to [clear it manually](https://www.elastic.co/guide/en/elasticsearch/reference/6.5/disk-allocator.html) like you did before.

---

<div class="post-metadata">

**Author:** ![planetvortex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/planetvortex/32/31080_2.png) [@planetvortex](https://discuss.elastic.co/u/planetvortex)\
**Post date:** [November 27, 2018, 5:06pm UTC](https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768/7 "2018-11-27T17:06:29Z")

</div>

Thank you, the cluster has cleared. I learned a new trick with this too and led me to the discover of this:  
GET \_cluster/allocation/explain

I had a lot of nodes with the wrong version of elasticsearch as well. They must've changed version in the yum repo the next day after I rebuilt the other nodes.

---

<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 25, 2018, 5:10pm UTC](https://discuss.elastic.co/t/issue-with-elastic-cluster-after-upgrade-to-6-5-0/157768/8 "2018-12-25T17:10:52Z")

</div>

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