# Some indexes stopped to rollover and are now created without alias

**URL:** <https://discuss.elastic.co/t/some-indexes-stopped-to-rollover-and-are-now-created-without-alias/325623>\
**Category:** Elasticsearch\
**Created:** [February 15, 2023, 2:08pm UTC](https://discuss.elastic.co/t/some-indexes-stopped-to-rollover-and-are-now-created-without-alias/325623 "2023-02-15T14:08:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zebu14](https://avatars.discourse-cdn.com/v4/letter/z/aca169/32.png) [@zebu14](https://discuss.elastic.co/u/zebu14)\
**Post date:** [February 15, 2023, 2:08pm UTC](https://discuss.elastic.co/t/some-indexes-stopped-to-rollover-and-are-now-created-without-alias/325623/1 "2023-02-15T14:08:59Z")

</div>

Hello,

Some weeks ago, I had a full disk problem on my dev cluster.  
I made some space, reactivated index writing with

```auto
PUT /_all/_settings
{
  "index.blocks.read_only_allow_delete": null
}

```

Most of the indexes are doing the rollover correctly since, but today I found that three of them decided to write without the configured alias, and they didn't rollover... leading to a new "no free space available"...  
My indexes usually have their name with "-00000" for the rollover alias part.

I don't know what prevents these 3 indexes to be named correctly to rollover...

Any help appreciated

---

<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:** [March 15, 2023, 2:09pm UTC](https://discuss.elastic.co/t/some-indexes-stopped-to-rollover-and-are-now-created-without-alias/325623/2 "2023-03-15T14:09:42Z")

</div>

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