# ILM pattern is incrementing by two numbers instead of one

**URL:** https://discuss.elastic.co/t/ilm-pattern-is-incrementing-by-two-numbers-instead-of-one/299882
**Category:** Elasticsearch
**Tags:** ilm-index-lifecycle-management
**Created:** [March 16, 2022, 5:05pm UTC](https://discuss.elastic.co/t/ilm-pattern-is-incrementing-by-two-numbers-instead-of-one/299882 "2022-03-16T17:05:04Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![adminunix](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adminunix](https://discuss.elastic.co/u/adminunix)
#### Post date: [March 16, 2022, 5:05pm UTC](https://discuss.elastic.co/t/ilm-pattern-is-incrementing-by-two-numbers-instead-of-one/299882/1 "2022-03-16T17:05:04Z")

</div>

Hi,

I have a strange issue with new backing indices creates after rollover. Suffix number is incrementing by two numbers instead of one.

![image](https://us1.discourse-cdn.com/elastic/original/3X/f/2/f2b83229912fac3920cb769438362ea78601a8b8.png)

![image](https://us1.discourse-cdn.com/elastic/original/3X/7/3/73fce1b03c68879cc6a241f22cf0e730cb8f05ec.png)

Initially, ILM generated new indices with correct names incrementing only one number, but now it increments two numbers.

Here are the logs:

```auto
[2022-03-16T08:07:04,977][INFO][o.e.x.i.IndexLifecycleTransition] [my-node-01] moving index [.ds-logstash-iib-pro-2022.02.21-000007] from [{"phase":"hot","action":"rollover","name":"check-rollover-ready"}] to [{"phase":"hot","action":"rollover","name":"attempt-rollover"}] in policy [logstash-pro]
[2022-03-16T08:07:05,531][INFO][o.e.c.m.MetadataCreateIndexService] [my-node-01] [.ds-logstash-iib-pro-2022.03.16-000009] creating index, cause [rollover_data_stream], templates [logstash-pro-template], shards [1]/[1]
[2022-03-16T08:07:05,655][INFO][o.e.x.i.IndexLifecycleTransition] [my-node-01] moving index [.ds-logstash-iib-pro-2022.03.16-000009] from [null] to [{"phase":"new","action":"complete","name":"complete"}] in policy [logstash-pro]
[2022-03-16T08:07:05,656][INFO][o.e.x.i.IndexLifecycleTransition] [my-node-01] moving index [.ds-logstash-iib-pro-2022.02.21-000007] from [{"phase":"hot","action":"rollover","name":"attempt-rollover"}] to [{"phase":"hot","action":"rollover","name":"wait-for-active-shards"}] in policy [logstash-pro]
[2022-03-16T08:07:05,837][INFO][o.e.x.i.IndexLifecycleTransition] [my-node-01] moving index [.ds-logstash-iib-pro-2022.03.16-000009] from [{"phase":"new","action":"complete","name":"complete"}] to [{"phase":"hot","action":"set_priority","name":"set_priority"}] in policy [logstash-pro]
[2022-03-16T08:07:05,837][INFO][o.e.x.i.IndexLifecycleTransition] [my-node-01] moving index [.ds-logstash-iib-pro-2022.02.21-000007] from [{"phase":"hot","action":"rollover","name":"wait-for-active-shards"}] to [{"phase":"hot","action":"rollover","name":"update-rollover-lifecycle-date"}] in policy [logstash-pro]
[2022-03-16T08:07:05,838][INFO][o.e.x.i.IndexLifecycleTransition] [my-node-01] moving index [.ds-logstash-iib-pro-2022.02.21-000007] from [{"phase":"hot","action":"rollover","name":"update-rollover-lifecycle-date"}] to [{"phase":"hot","action":"rollover","name":"set-indexing-complete"}] in policy [logstash-pro]
[2022-03-16T08:07:06,027][INFO][o.e.x.i.IndexLifecycleTransition] [my-node-01] moving index [.ds-logstash-iib-pro-2022.03.16-000009] from [{"phase":"hot","action":"set_priority","name":"set_priority"}] to [{"phase":"hot","action":"unfollow","name":"branch-check-unfollow-prerequisites"}] in policy [logstash-pro]
[2022-03-16T08:07:06,028][INFO][o.e.x.i.IndexLifecycleTransition] [my-node-01] moving index [.ds-logstash-iib-pro-2022.02.21-000007] from [{"phase":"hot","action":"rollover","name":"set-indexing-complete"}] to [{"phase":"hot","action":"complete","name":"complete"}] in policy [logstash-pro]
[2022-03-16T08:07:06,071][INFO][o.e.x.i.IndexLifecycleTransition] [my-node-01] moving index [.ds-logstash-iib-pro-2022.03.16-000009] from [{"phase":"hot","action":"unfollow","name":"branch-check-unfollow-prerequisites"}] to [{"phase":"hot","action":"rollover","name":"check-rollover-ready"}] in policy [logstash-pro]

```

Any reason for this situation? Is this a bug?

Thanks.

---

<div class="post-metadata">

### Author: ![adminunix](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adminunix](https://discuss.elastic.co/u/adminunix)
#### Post date: [March 25, 2022, 12:31pm UTC](https://discuss.elastic.co/t/ilm-pattern-is-incrementing-by-two-numbers-instead-of-one/299882/2 "2022-03-25T12:31:44Z")

</div>

Nobody has the same issue with data\_stream indices?

---

<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: [April 22, 2022, 12:31pm UTC](https://discuss.elastic.co/t/ilm-pattern-is-incrementing-by-two-numbers-instead-of-one/299882/3 "2022-04-22T12:31:45Z")

</div>

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