Lots of o.o.i.i.ManagedIndexRunner Executing attempt_transition_step messages

OpenSearch
1

I’m seeing a lot of these messages in our opensearch logs:

[2022-07-18T09:19:40,242][INFO ][o.o.j.s.JobScheduler     ] [FQDN] Will delay 95200 miliseconds for next execution of job filebeat-7.15.0-2022.06.14
[2022-07-18T09:19:41,104][INFO ][o.o.i.i.ManagedIndexRunner] [FQDN] Executing attempt_transition_step for filebeat-7.15.0-2022.06.14
[2022-07-18T09:19:41,105][INFO ][o.o.i.i.ManagedIndexRunner] [FQDN] Finished executing attempt_transition_step for filebeat-7.15.0-2022.06.14
[2022-07-18T09:23:36,313][INFO ][o.o.j.s.JobScheduler     ] [FQDN] Will delay 98995 miliseconds for next execution of job filebeat-7.15.0-2022.06.14
[2022-07-18T09:23:36,753][INFO ][o.o.i.i.ManagedIndexRunner] [FQDN] Executing attempt_transition_step for filebeat-7.15.0-2022.06.14
[2022-07-18T09:23:36,754][INFO ][o.o.i.i.ManagedIndexRunner] [FQDN] Finished executing attempt_transition_step for filebeat-7.15.0-2022.06.14
[2022-07-18T09:28:40,108][INFO ][o.o.j.s.JobScheduler     ] [FQDN] Will delay 142218 miliseconds for next execution of job filebeat-7.15.0-2022.06.14
[2022-07-18T09:28:41,167][INFO ][o.o.i.i.ManagedIndexRunner] [FQDN] Executing attempt_transition_step for filebeat-7.15.0-2022.06.14
[2022-07-18T09:28:41,168][INFO ][o.o.i.i.ManagedIndexRunner] [FQDN] Finished executing attempt_transition_step for filebeat-7.15.0-2022.06.14

for lots of indexes. If this just ILM doing its thing? If so, it’s very chatty.

1 Like
2

I’m seeing a very similar logging. Did you find a solution or any further information about your issue?
Our’s constantly going:

2023-02-13T10:43:44.965+00:00 [2023-02-13T10:43:44,965][INFO ][o.o.i.i.ManagedIndexRunner] [xxx] Executing attempt_rollover for -000001
2023-02-13T10:43:44.969+00:00 [2023-02-13T10:43:44,969][INFO ][o.o.i.i.ManagedIndexRunner] [xxx] Finished executing attempt_rollover for -000001
2023-02-13T10:43:44.969+00:00 [2023-02-13T10:43:44,969][INFO ][o.o.i.i.ManagedIndexRunner] [xxx] Finished executing attempt_rollover for -000001
2023-02-13T10:43:45.137+00:00 [2023-02-13T10:43:45,137][INFO ][o.o.j.s.JobScheduler ] [xxx] Will delay 117367 miliseconds for next execution of job -000001

3

I never got any more information. I’m still seeing the same things with 2.5.0.

4

Thanks! ours seems to be affecting only 2 of 12 nodes.

5

I am using Opensearch 2.5.0. I keep getting this in log and this keeps happening infinitely. The ISM policy never runs

[2023-07-02T19:12:57,200][INFO ][o.o.j.s.JobSweeper       ] [opensearch-cluster-master-2] Running full sweep
[2023-07-02T19:13:38,500][INFO ][o.o.j.s.JobScheduler     ] [opensearch-cluster-master-2] Will delay 85129 miliseconds for next execution of job xxx-2023.06.01

On the managed index page it says Still initializing, please wait a moment.and this stays like this forever. I have already tried steps from Index Policy Still initializing - #16 by Oli no luck