Update stack upgrade docs re upgrade assistant #24
Conversation
| . We recommend upgrading to 5.6 and using the | ||
| {xpack-ref}/xpack-upgrade-assistant.html[Upgrade Assistant]'s Reindex Helper to | ||
| reindex 2.x indices. Alternatively, you can manually {ref}/docs-reindex.html[reindex] | ||
| or delete all 2.x indices. |
There was a problem hiding this comment.
My reasoning here is that we really should be pushing our Upg Asst tool. Using the reindex API to manually upgrade is an option, but it shouldn't be the first thing we suggest.
| Starting in 5.6, X-Pack Kibana provides an | ||
| {xpack-ref}/xpack-upgrade-assistant.html[Upgrade Assistant UI] to aid in the | ||
| upgrade process. Use this utility to upgrade the internal Kibana and X-Pack | ||
| indices. |
There was a problem hiding this comment.
The original text is misleading-- you don't get a list of all indices that need upgrading or reindexing from the assistance API because Kibana indices will not show up in the response.
In addition, the instructions for upgrading the internal indices only applies to x-pack indices--not to Kibana. So I created two sections under this header--one for manually upgrading x-pack internal indices, and one for manually upgrading kibana indices. At the top of both of these sections, I have highlighted the the Upgrade Assistant tool which does both/all from a UI.
I removed the TIP as well because that wording was actually incorrect.
Targetting 6.0
This will be forward ported to everything 6.0+. Actually does this need to appear in the 5.6 docs?
The changes here reflect my thoughts on some aspects of the docs that are still misleading.