diff --git a/docs/en/install-upgrade/upgrading-stack.asciidoc b/docs/en/install-upgrade/upgrading-stack.asciidoc index 72f1d6a6d..07237c2b7 100644 --- a/docs/en/install-upgrade/upgrading-stack.asciidoc +++ b/docs/en/install-upgrade/upgrading-stack.asciidoc @@ -517,9 +517,7 @@ POST _transform/my-transform/_reset ==== When {kib} Upgrade Assistant reindexes the documents, {kib} will put a write block on the old destination index, copy the results to a new index, delete the old index, and create an alias to the new index. During this time, the {transform} will pause and wait for the destination to become writable again. If you do not want the {transform} to pause, continue to <>. -If an index is less than 10GB of size, we recommend using {kib}'s Upgrade Assistant to automatically migrate the index. - -If an index size is greater than 10 GB it is recommended to use the Reindex API. Reindexing consists of the following steps: +If an index size is less than 10 GB, we recommend using {kib}'s Upgrade Assistant to automatically migrate the index. You can use the https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-indices-1[Get index information API] to obtain the size of an index: @@ -528,9 +526,7 @@ You can use the https://www.elastic.co/docs/api/doc/elasticsearch/operation/oper GET _cat/indices/.transform-destination-example?v&h=index,store.size ---- -The reindexing can be initiated in the {kib} Upgrade Assistant. - -If an index size is greater than 10 GB, it is recommended to use the Reindex API. Reindexing consists of the following steps: +If an index size is greater than 10 GB, we recommend using the Reindex API. Reindexing consists of the following steps: . Set the original index to read-only. +