From 85139fad7ea7bda736e5aee65f9f1c7007f98fd9 Mon Sep 17 00:00:00 2001 From: Jake Landis Date: Wed, 15 Apr 2020 07:55:31 -0500 Subject: [PATCH] [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 --- docs/reference/ilm/ilm-with-existing-indices.asciidoc | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/reference/ilm/ilm-with-existing-indices.asciidoc b/docs/reference/ilm/ilm-with-existing-indices.asciidoc index 3ebf0a1fd9a..f2e2f5e7665 100644 --- a/docs/reference/ilm/ilm-with-existing-indices.asciidoc +++ b/docs/reference/ilm/ilm-with-existing-indices.asciidoc @@ -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