# Resetting Cluster from Read-Only

**URL:** <https://discuss.elastic.co/t/resetting-cluster-from-read-only/140577>\
**Category:** Elasticsearch\
**Created:** [July 18, 2018, 2:30pm UTC](https://discuss.elastic.co/t/resetting-cluster-from-read-only/140577 "2018-07-18T14:30:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trevor\_Mills](https://avatars.discourse-cdn.com/v4/letter/t/a9adbd/32.png) [@Trevor\_Mills](https://discuss.elastic.co/u/Trevor_Mills)\
**Post date:** [July 18, 2018, 2:30pm UTC](https://discuss.elastic.co/t/resetting-cluster-from-read-only/140577/1 "2018-07-18T14:30:13Z")

</div>

I have a single node cluster that previously had XPack installed. I have since removed XPack.

Today, my disk usage reached the flood water mark and so Elasticsearch put all blocks into `read_only_allow_delete`.

I cleared diskspace, and attempted to reset all blocks by running this in Kibana:

```auto
curl -XPUT -H "Content-Type: application/json" https://[YOUR_ELASTICSEARCH_ENDPOINT]:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'

```

I received an error though:

```auto
{
  "error": {
    "root_cause": [
      {
        "type": "illegal_argument_exception",
        "reason": "unknown setting [index.xpack.watcher.template.version] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "unknown setting [index.xpack.watcher.template.version] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"
  },
  "status": 400
}

```

I don't know how to get around this. It looks like something is still trying to use an xpack setting. Does anyone have any ideas?

Thanks,  
Trevor

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 19, 2018, 1:07am UTC](https://discuss.elastic.co/t/resetting-cluster-from-read-only/140577/2 "2018-07-19T01:07:28Z")

</div>

Ping @spinscale for an idea on what this might be?

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [July 19, 2018, 1:13am UTC](https://discuss.elastic.co/t/resetting-cluster-from-read-only/140577/3 "2018-07-19T01:13:24Z")

</div>

What version of Elasticsearch are you running?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [July 19, 2018, 7:56am UTC](https://discuss.elastic.co/t/resetting-cluster-from-read-only/140577/4 "2018-07-19T07:56:53Z")

</div>

This stems from the watcher history indices, which have this settings set. Due to problems like this from 6.3.0 onwards the watcher history is using metadata instead of a dedicated setting for this, see [https://github.com/elastic/elasticsearch/pull/30832](https://github.com/elastic/elasticsearch/pull/30832)

If you don't need the watcher history indices anymore, you could try to delete them first. Otherwise you would need to reinstall x-pack again, but disable all the features (using `xpack.security.enabled: false` and so forth.

Hope this helps!

---

<div class="post-metadata">

**Author:** ![Trevor\_Mills](https://avatars.discourse-cdn.com/v4/letter/t/a9adbd/32.png) [@Trevor\_Mills](https://discuss.elastic.co/u/Trevor_Mills)\
**Post date:** [July 19, 2018, 1:12pm UTC](https://discuss.elastic.co/t/resetting-cluster-from-read-only/140577/5 "2018-07-19T13:12:06Z")

</div>

I'm on 6.2

---

<div class="post-metadata">

**Author:** ![Trevor\_Mills](https://avatars.discourse-cdn.com/v4/letter/t/a9adbd/32.png) [@Trevor\_Mills](https://discuss.elastic.co/u/Trevor_Mills)\
**Post date:** [July 19, 2018, 1:12pm UTC](https://discuss.elastic.co/t/resetting-cluster-from-read-only/140577/6 "2018-07-19T13:12:45Z")

</div>

That was it. I did `DELETE .watcher-history-*` in Kibana and now the settings call succeeds. Thanks very much.

---

<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:** [August 16, 2018, 1:25pm UTC](https://discuss.elastic.co/t/resetting-cluster-from-read-only/140577/7 "2018-08-16T13:25:18Z")

</div>

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