[7.x] Advise a simpler curator migration (#54457) (#55188)

Advice for migrating from Curator should simply be to phase out curator managed indices, 
since curator will ignore ILM indices
https://www.elastic.co/guide/en/elasticsearch/client/curator/5.7/ilm-and-curator.html#ilm-and-curator.

Co-authored-by: Jay Greenberg <PhaedrusTheGreek@users.noreply.github.com>
This commit is contained in:
Jake Landis 2020-04-15 07:55:31 -05:00 committed by GitHub
parent d8b43c6283
commit 85139fad7e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 5 deletions

View File

@ -3,13 +3,14 @@
[[ilm-with-existing-indices]]
== Manage existing indices
NOTE: If migrating from Curator, ensure you are running Curator version 5.7 or greater
so that Curator will ignore ILM managed indices.
While it is recommended to use {ilm-init} to manage the index lifecycle from
start to finish, it may be useful to use {ilm-init} with existing indices,
particularly when transitioning from an alternative method of managing the index
lifecycle such as Curator, or when migrating from daily indices to
rollover-based indices. Such use cases are fully supported, but there are some
configuration differences from when {ilm-init} can manage the complete index
lifecycle.
for example, when migrating from daily indices to rollover-based indices.
Such use cases are fully supported, but there are some configuration differences
from when {ilm-init} can manage the complete index lifecycle.
This section describes strategies to leverage {ilm-init} for existing periodic
indices when migrating to fully {ilm-init}-manged indices, which can be done in