APM Index Went Warm Without Rolling Over

There was an issue with my APM indexes in that rolling over was disabled. They all went warm without rolling over. I updated the index so it allows writes and updated the ILM policy to allow rolling over.

For the last week all data in the APM indexes has been written to my warm indexes.. is there a way to force the rollover for these indexes to force the 0001 to 0002 and create a new 0001?


OR.. would it be possible to promote a warm index back to hot in order for the ILM hot -> warm policy to organically just re-run?

I ended up resolving this issue myself by copying the old indexes using the Reindex method in the API, then deleting the old indexes. This kept my historical data and also forced the current APM policy to go into effect.

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