# My index write api request blocked by status 403 after adding index lifecycle policy

**URL:** <https://discuss.elastic.co/t/my-index-write-api-request-blocked-by-status-403-after-adding-index-lifecycle-policy/333174>\
**Category:** Elasticsearch\
**Created:** [May 11, 2023, 9:01am UTC](https://discuss.elastic.co/t/my-index-write-api-request-blocked-by-status-403-after-adding-index-lifecycle-policy/333174 "2023-05-11T09:01:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeyong.oh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeyong.oh/32/120905_2.png) [@jeyong.oh](https://discuss.elastic.co/u/jeyong.oh)\
**Post date:** [May 11, 2023, 9:01am UTC](https://discuss.elastic.co/t/my-index-write-api-request-blocked-by-status-403-after-adding-index-lifecycle-policy/333174/1 "2023-05-11T09:01:46Z")

</div>

This is what happened today.

1. I'm using index without life cycle management. The index name is "vehicle-iot-coordinate", it's size is about 280GB and it grow with rate of 1GB/day.
2. I'm adding lifecycle management. (disable rollover, only has hot, frozen, delete phase. Move data to frozen after 14 days,.)
3. As soon as I adding ILM, my hot instance's disk allocation is spiked to 100%, so I doubled my instance size.
4. After the deployment is successful, my server raise error.

```auto
{
  "error": {
    "root_cause": [
      {
        "type": "cluster_block_exception",
        "reason": "index [partial-vehicle-iot-coordinate] blocked by: [FORBIDDEN/8/index write (api)];"
      }
    ],
    "type": "cluster_block_exception",
    "reason": "index [partial-vehicle-iot-coordinate] blocked by: [FORBIDDEN/8/index write (api)];"
  },
  "status": 403
}

```

I already did the api with this.

```auto
{
  "index.blocks.read_only_allow_delete": null,
  "index.blocks.write": null
}

```

But it raise this error.

```auto
{
    "error": {
        "root_cause": [
            {
                "type": "illegal_argument_exception",
                "reason": "illegal value can't update [index.blocks.write] from [true] to [false]"
            }
        ],
        "type": "illegal_argument_exception",
        "reason": "illegal value can't update [index.blocks.write] from [true] to [false]",
        "caused_by": {
            "type": "illegal_argument_exception",
            "reason": "Cannot remove write block from searchable snapshot index"
        }
    },
    "status": 400
}

```

Please help.

---

<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:** [June 8, 2023, 9:02am UTC](https://discuss.elastic.co/t/my-index-write-api-request-blocked-by-status-403-after-adding-index-lifecycle-policy/333174/2 "2023-06-08T09:02:37Z")

</div>

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