Skip to content

Fixes redundancy in the Transforms migration section #3013

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 7, 2025
Merged

Fixes redundancy in the Transforms migration section #3013

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
55c6b14
Fixes redundancy in the Transforms migration section
kosabogi Apr 3, 2025
83c5553
Update docs/en/install-upgrade/upgrading-stack.asciidoc
kosabogi Apr 4, 2025
63bb3c3
Update docs/en/install-upgrade/upgrading-stack.asciidoc
kosabogi Apr 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions docs/en/install-upgrade/upgrading-stack.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <<reindexing-transform-running, reindexing the {transform}'s destination index while the {transform} is running>>.

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:

Expand All @@ -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.
+
Expand Down