# Index Lifecycle Error- Check rollover ready

**URL:** https://discuss.elastic.co/t/index-lifecycle-error-check-rollover-ready/208556
**Category:** Elasticsearch
**Created:** [November 19, 2019, 6:04pm UTC](https://discuss.elastic.co/t/index-lifecycle-error-check-rollover-ready/208556 "2019-11-19T18:04:44Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Mehak\_Bhargava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehak_bhargava/32/54750_2.png) [@Mehak\_Bhargava](https://discuss.elastic.co/u/Mehak_Bhargava)
#### Post date: [November 19, 2019, 6:04pm UTC](https://discuss.elastic.co/t/index-lifecycle-error-check-rollover-ready/208556/1 "2019-11-19T18:04:44Z")

</div>

After I ran these queries, my filebeat index isn't collecting data on discover and gives me following error-

```auto
PUT filebeat-7.4.0-2019.11.08-000001/_settings
    {
    "index": {
    "blocks": {
    "read_only_allow_delete": "false"
    }
    }
}
    
    POST /filebeat-7.4.0-2019.11.08-000001/_shrink/filebeat-7.4.0-2019.11.18-000001
{
  "settings": {
    "index.routing.allocation.require._name": null, 
    "index.blocks.write": true
  }
}

```

Error-

```auto
Index lifecycle error
cluster_block_exception: index [filebeat-7.4.0-2019.11.08-000001] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];

```

The error also says, Current Action: rollover and Failed Step: check-rollover-ready. Please help how to undo this.

---

<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 17, 2019, 6:04pm UTC](https://discuss.elastic.co/t/index-lifecycle-error-check-rollover-ready/208556/2 "2019-12-17T18:04:52Z")

</div>

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