# FORBIDDEN/8/index write (api) - During date change on indexes

**URL:** https://discuss.elastic.co/t/forbidden-8-index-write-api-during-date-change-on-indexes/179319
**Category:** Elasticsearch
**Tags:** ilm-index-lifecycle-management
**Created:** [May 2, 2019, 9:11am UTC](https://discuss.elastic.co/t/forbidden-8-index-write-api-during-date-change-on-indexes/179319 "2019-05-02T09:11:17Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)
#### Post date: [May 14, 2019, 2:22am UTC](https://discuss.elastic.co/t/forbidden-8-index-write-api-during-date-change-on-indexes/179319/7 "2019-05-14T02:22:18Z")

</div>

> [@KevSex](#):
>
> So I take it, a `force merge` doesn't have a prerequisite to set the index to read-only?

Nope, no prerequisite for that.

> [@KevSex](#):
>
> 1. Updated elasticsearch outputs to include `manage_template => false`
> 2. Update Index Lifecycle Management warm phase `min_age` value to `25h`
> 
> This has stopped the issue from occurring but looking to confirm which of the above affected this. I'd like to say the ILM change as the elasticsearch output had been working fine without the `manage_template` parameter and it was ILM that was recently updated.
> 
> Can anyone confirm?

I don't think either of those would cause anything related to the index being read-only. Is it possible that your node filled up with disk space and the index was marked read only because of that?

---

_[View the full topic](https://discuss.elastic.co/t/forbidden-8-index-write-api-during-date-change-on-indexes/179319)._