* Migrations v2 docs
* Not all kibana distributions automatically restarted a killed process
* Mention that we add a write block to the outdated index
* Formating: collapse three notes into a single note with three bullet points
* Update docs/setup/upgrade/upgrade-standard.asciidoc
Co-authored-by: Josh Dover <1813008+joshdover@users.noreply.github.com>
* Add table of outdated / upgraded indices per version of Kibana
* Review feedback: separate section for multi-instance upgrade migrations
* Review feedback: link to saved objects management
* Review feedback: stronger wording for not deleting any indices
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Josh Dover <1813008+joshdover@users.noreply.github.com>
* Resolving failed Kibana upgrade migrations
* Move warning against rolling upgrades into upgrade-standard and call out stopping all instances in specific upgrade steps
* Add preventing migration failures section
* Add incompatible xpack.tasks.index: .tasks setting to preventing migration failures
* Fix link
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Add a note about index migrations to the kibana setup docs
* Tewak the migrations asciidocs for clarity
* docs: refine saved object migration details
Breaking down the migration process into sections helps people find
and link to relevant information more easily.
The focus is on ongoing maintenance of Kibana, whereas the initial new
experience in 6.5.0 is treated as a note of clarification.
Error handling should be expanded in the future to include details about
specific known error cases.
These changes include all three known upgrade scenarios:
1. New installation (K3 -> K5)
2. Standard upgrade (K4.2 -> K5)
3. Standard upgrade with reindex (K4.1 -> K5)
