github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 09:19:04 -04:00
Code Issues Projects Releases Packages Wiki Activity

Removes non-backup rollback from upgrade kibana (#189011)

Browse source 
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 <elasticmachine@users.noreply.github.com>
This commit is contained in:
Christiane (Tina) Heiligers 2024-07-24 07:51:24 -07:00 • committed by GitHub
parent c9bc0c3cd7
commit f2aa1faee4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 0 additions and 37 deletions
Download patch file Download diff file Expand all files Collapse all files

37
docs/setup/upgrade/rollback-migration.asciidoc
View file

@ -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.