I’ve been trying out managed indexes. Setup and getting the initial state seem fine, however all my indexes show an action of “Transition” with info listed as “Attempting to Transition”. Is this expected behavior? Are there instructions for where I can go to debug/diagnose further?

Hi @tschaible , The “transition” action is the internal action used for transitioning between states. It means your managed index has finished the actions in its current state and is attempting to transition to a new one which will happen once the condition is true. Can you post an example of your …

Sure, the index policy is meant to manage indexes auto-created by fluentd. Fluentd creates them with a date-key automatically. The example is below, but it’s intended to simply start them as “hot”, move them to “cold” (read-only) after the day is done, and then delete them after 30 days. { "p…

Yep, that’s the correct behavior. It’s now waiting for the condition to be met before it transitions to the specified state. Agree, we can better document and give better messages. Possibly listing the different conditions checked and the current values might be helpful. Will create a GitHub issue …

Hello, it doesn’t work in my case and stuck in this state. My index is actually older than 7 days, but it is still in the hot phase. What should I do? { "id": "opensearch_prod_app_logs_delete_after_90d", "seqNo": 50341, "primaryTerm": 1, "policy": { "policy_id": "opensearc…

Hi @okapko , How long has it been in the Evaluating transitions phase? If it just moved into that then it can take up to 30-48 minutes to actually trigger the transition. Otherwise can you post the response of these two API calls (and redact anything you need to): GET _opendistro/_ism/explain/<IND…

Actually, I recently updated the State management policy and decreased the transition period for the hot → warm phase from 26 days to 7 days to check how it works and how quick search works over warm indexes. So at this moment, I’ve got a few dozens of indexes that are older than 7 days, but they a…

When you make changes to a policy, it does not retroactively apply to existing indices that are using that policy. This is to ensure that those existing indices don’t enter a bad state depending on what the change to the policy was. So from the sounds of it, those indices are still using the policy …

Thanks, @dbbaughe Got it. Will try to do it using Change Policy API.

POST _opendistro/_ism/change_policy/prod-app-blah-blah-2022.03.09 { "policy_id": "opensearch_prod_app_logs_delete_after_90d" } GET _opendistro/_ism/explain/prod-app-blah-blah-api-2022.03.09 { "prod-app-worldpac-api-2022.03.09" : { "index.plugins.index_state_management.policy_id" : "opensea…

[Знімок екрана 2022-03-18 о 20.35.59] UPDATE It’s working, thanks a lot @dbbaughe

Stuck in "Attempting to transition"

Plugins Index Management

okapko March 18, 2022, 6:36pm 11

UPDATE
It’s working, thanks a lot @dbbaughe

Hot/ultrawarm policy

Topic		Replies	Views
How to Alert on "Failed Transition State" for a Managed Index Index Management	1	687	November 2, 2020
Managed indices are stuck in Evaluating transition conditions Index Management	0	1070	June 20, 2022
Policy managed index stuck on Evaluating transition conditions OpenSearch index-management	2	52	May 13, 2026
Unable to change managed index policy Index Management	0	332	February 1, 2024
Policy for deletion after 90d stuck in evaluating transition conditions Index Management troubleshoot	2	1365	July 7, 2022

Stuck in "Attempting to transition"

Related topics