You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reason: Mappings or index settings are changed in templates and an index rollover is necessary to pick up the change. The change needs to be immediate and you can't wait for the index to roll normally.
Process:
Currently I do the following.
Create a new index with an incremented number
API call to _alias to set is_write_index to false on the current one and true on the new one.
Update _settings on the original index to index.lifecycle.indexing_complete: true
Those 3 steps are kind of pain to do by hand or lookup. I wrote a wrapper python script that does this, but it seems like it would be easy just to create a new API call to perform this.
The text was updated successfully, but these errors were encountered:
tarp2699
changed the title
provide an API to manually rollover an index that currently has an ILM policy
enhancement: provide an API to manually rollover an index that currently has an ILM policy
Nov 27, 2019
I have good news: This is already implemented! See #47324 - as of 7.5, you'll be able to just call the rollover API manually and ILM will figure it out and continue working as you would expect.
Because this has already been addressed, I'm going to close this issue. Please comment further if the above feature does not address your needs and we can discuss further.
(edit: also see #44175 for the original issue and discussion which lead to the linked PR)
Reason: Mappings or index settings are changed in templates and an index rollover is necessary to pick up the change. The change needs to be immediate and you can't wait for the index to roll normally.
Process:
Currently I do the following.
Those 3 steps are kind of pain to do by hand or lookup. I wrote a wrapper python script that does this, but it seems like it would be easy just to create a new API call to perform this.
The text was updated successfully, but these errors were encountered: