From 1ab69490cc41398375df0479ac4714435dd27237 Mon Sep 17 00:00:00 2001 From: "Christiane (Tina) Heiligers" Date: Wed, 24 Jul 2024 07:51:24 -0700 Subject: [PATCH] Removes non-backup rollback from upgrade kibana (#189011) FIx https://github.com/elastic/kibana/issues/158117 Removes section on rolling back without a snapshot. The changes made to kibana saved objects migration make the process of rolling back without a snapshot too complex for customers to do alone. Furthermore, rolling back without a snapshot is not recommended or supported. See the changes on `master` [here](https://kibana_bk_189011.docs-preview.app.elstc.co/guide/en/kibana/master/upgrade-migrations-rolling-back.html) Co-authored-by: Elastic Machine (cherry picked from commit f2aa1faee4b05f3aa2d8f21bb7e63aff357cdd9b) --- .../setup/upgrade/rollback-migration.asciidoc | 37 ------------------- 1 file changed, 37 deletions(-) diff --git a/docs/setup/upgrade/rollback-migration.asciidoc b/docs/setup/upgrade/rollback-migration.asciidoc index 6415a7a62a71a..ced12455ff845 100644 --- a/docs/setup/upgrade/rollback-migration.asciidoc +++ b/docs/setup/upgrade/rollback-migration.asciidoc @@ -30,40 +30,3 @@ POST _snapshot/my_repository/my_snapshot_2099.05.06/_restore -------------------------------------------- <1> Exclude all indices and data streams from the restore operation to ensure that only the {kib} system indices included in the {kib} feature state will be restored. . Start all {kib} instances on the older version you want to rollback to. - -[float] -==== (Not supported) Roll back without a backup snapshot - -WARNING: Rolling back without a backup snapshot is not supported and will be removed in a future version of {kib}. - -. To make sure no {kib} instances are performing an upgrade migration, shut down all {kib} instances. -. {ref}/snapshots-take-snapshot.html[Take a snapshot] that includes the `kibana` feature state. By default, snapshots include the `kibana` feature state. -. Delete the version-specific indices created by the failed upgrade migration. -+ -For example, to rollback from a failed upgrade -to v7.12.0, enter: -+ -[source,sh] --------------------------------------------- -DELETE /.kibana_7.12.0_*,.kibana_task_manager_7.12.0_* --------------------------------------------- - -. Inspect the output of `GET /_cat/aliases`. -+ -If the `.kibana` or `.kibana_task_manager` aliases are missing, you must create them manually. -Find the latest index from the output of `GET /_cat/indices` and create the missing alias to point to the latest index. -For example, if the `.kibana` alias is missing, and the latest index is `.kibana_3`, create a new alias using: -+ -[source,sh] --------------------------------------------- -POST /.kibana_3/_aliases/.kibana --------------------------------------------- - -. To remove the write block from the roll back indices, enter: -+ -[source,sh] --------------------------------------------- -PUT /.kibana,.kibana_task_manager/_settings {"index.blocks.write": false} --------------------------------------------- - -. Start {kib} on the older version you want to roll back to.