From 101ea0549a824e49c1ed6040408e9a96db6fdd0e Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Thu, 13 Oct 2016 12:12:53 +0200 Subject: [PATCH] Add note about retention periods to reindex-upgrade docs --- docs/reference/setup/reindex_upgrade.asciidoc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/reference/setup/reindex_upgrade.asciidoc b/docs/reference/setup/reindex_upgrade.asciidoc index 8ee9c61e424..f9e7a60ee5b 100644 --- a/docs/reference/setup/reindex_upgrade.asciidoc +++ b/docs/reference/setup/reindex_upgrade.asciidoc @@ -19,6 +19,20 @@ If you are running an Elasticsearch 2.x cluster or older, you have two options: * Create a new 6.x cluster and use reindex-from-remote to import indices directly from the 2.x cluster. See <>. +.Time-based indices and retention periods +******************************************* + +For many use cases with time-based indices, you will not need to worry about +carrying old 2.x indices with you to 6.x. Data in time-based indices usually +becomes less interesting as time passes. Old indices can be deleted once they +fall outside of your retention period. + +Users in this position can continue to use 5.x until all old 2.x indices have +been deleted, then upgrade to 6.x directly. + +******************************************* + + [[reindex-upgrade-inplace]] ==== Reindex in place