# No rollover with data stream lifecycle

**URL:** https://discuss.elastic.co/t/no-rollover-with-data-stream-lifecycle/382165
**Category:** Elasticsearch
**Created:** [September 23, 2025, 1:04pm UTC](https://discuss.elastic.co/t/no-rollover-with-data-stream-lifecycle/382165 "2025-09-23T13:04:16Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![mikehaertl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikehaertl/32/145145_2.png) [@mikehaertl](https://discuss.elastic.co/u/mikehaertl)
#### Post date: [September 23, 2025, 4:18pm UTC](https://discuss.elastic.co/t/no-rollover-with-data-stream-lifecycle/382165/3 "2025-09-23T16:18:42Z")

</div>

Thanks, I will check the TRACE log.

Meanwhile it rolled over - but probably for other reasons that I’d expected:

> Desired balance computation for [37] is still not converged after [3.2h] and [1] iterations  
> Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.ds-logs-prod2-nlc-2025. 09.23-000002][0]]]).  
> Data stream lifecycle successfully rolled over datastream [logs-prod2-nlc] due to the following met _**rollover conditions [[max\_age: 1 d]**_, [min\_docs: 1]]. The new index is [.ds-logs-prod2-nlc-2025.09.23-000002]  
> [.ds-logs-prod2-nlc-2025.09.23-000002/gjKaOODPRvGWUCdaH8qjVQ] update\_mapping [\_doc]  
> [.ds-logs-prod2-nlc-2025.09.23-000002/gjKaOODPRvGWUCdaH8qjVQ] update\_mapping [\_doc]  
> [.ds-logs-prod2-nlc-2025.09.23-000002/gjKaOODPRvGWUCdaH8qjVQ] update\_mapping [\_doc]  
> Data stream lifecycle service successfully updated settings [[index.merge.policy.merge\_factor, index.merge.policy.floor\_segment]] for index index [.ds-logs-prod2-nlc-2025.09.22-000001]  
> Data stream lifecycle is issuing a request to _ **force merge** _ index [.ds-logs-prod2-nlc-2025.09.22-000001]  
> Data stream lifecycle successfully force merged index [.ds-logs-prod2-nlc-2025.09.22-000001]  
> [.ds-logs-prod2-nlc-2025.09.23-000002/gjKaOODPRvGWUCdaH8qjVQ] update\_mapping [\_doc]

It looks like the rollover happened after `1d`.

Also is it normal to see a force merge? The docs say that it should rather do a “tail merge” (whatever that exactly means)…

Could it be that I still see some remains of the previously configured ILM policy on the index (even though `prefer_ilm` is `false` now)?

---

_[View the full topic](https://discuss.elastic.co/t/no-rollover-with-data-stream-lifecycle/382165)._