maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[DOCS] Adds note to troubleshooting migration topic (#46815) (#46827)

Browse source
This commit is contained in:
gchaps 2019-09-27 10:57:48 -07:00 committed by GitHub
parent 4518ac4eac
commit eb19c7a3c9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/setup/upgrade/upgrade-migrations.asciidoc
View file

@ -46,7 +46,10 @@ The first instance that triggers saved object migrations will run the entire pro
[[upgrade-migrations-rolling-back]]
==== Rolling back to a previous version of {kib}
When rolling {kib} back to a previous version, point the `.kibana` alias to the appropriate {kib} index. When you have the previous version running again, delete the more recent `.kibana_N` index or indices so that future upgrades are based on the current {kib} index.
When rolling {kib} back to a previous version, point the `.kibana` alias to
the appropriate {kib} index. When you have the previous version running again,
delete the more recent `.kibana_N` index or indices so that future upgrades are
based on the current {kib} index. You must restart {kib} to re-trigger the migration.
WARNING: Rolling back to a previous {kib} version can result in saved object data loss if you had successfully upgraded and made changes to saved objects before rolling back.