7.0 upgrade #242
7.0 upgrade #242
Conversation
| ---------------------------------------------------------- | ||
| license -d @license.json | ||
| ---------------------------------------------------------- | ||
| . Back up your data. You **cannot roll back** to an earlier version unless |
There was a problem hiding this comment.
I ran into a problem when I included the .kibana index in my snapshot. When I subsequently tried to restore this index it conflicted with the existing one. Can someone from @elastic/kibana-platform tell me if this was user error on my part or if it is expected?
If expected, then we should update the docs with guidance on avoiding this pitfall.
There was a problem hiding this comment.
This feels like general snapshot/restore behavior--you can't restore on top of an open index. As far as the upgrade process goes, we tell folks to back up their data, but don't really get into how to use the snapshot if the upgrade goes sideways. (I made the implicit assumption that they would understand how to use the backup if they needed to.) It might make sense to add a few words when we add the info about what to do if you have a "broken upgrade".
There was a problem hiding this comment.
This feels like general snapshot/restore behavior--you can't restore on top of an open index.
Thanks Deb! That makes sense.
It might make sense to add a few words when we add the info about what to do if you have a "broken upgrade".
Yes, that would be very helpful! Including a note about what this means for Kibana would also be helpful, I think. Something along the lines of, "Note for Kibana users: If you're restoring a snapshot that contains the .kibana index, you'll need to shut Kibana down, close the index, and restore using the command line".
| ---------------------------------------------------------- | ||
| .. {es} Hadoop: {hadoop-ref}/install.html[install instructions] | ||
| .. {es}: {ref}/setup-upgrade.html[upgrade instructions] | ||
| .. Kibana: {kibana-ref}/upgrade.html[upgrade instructions] |
There was a problem hiding this comment.
Per feedback from @tylersmalley, this is a little more complicated if you're using Kibana. Because Kibana comes with a new Upgrade Assistant which tells you if there are problems with your indices and cluster, the order should be:
- Once the user is on 6.7, go into Kibana and view the Upgrade Assistant. Address all critical items.
- Follow the ES upgrade steps.
- Follow the Kibana upgrade steps.
For context, here's what the Upgrade Assistant looks like (this screenshot may contain bugs so it's not appropriate for use in the docs):
|
Will address CJ's comments in a separate PR. |
* [DOCS] First pass at 7.0 upgrade update. * [DOCS] Fixed formatting issues & flagged the Upgrade Assistant as xpack. * Update docs/en/install-upgrade/upgrading-stack.asciidoc Co-Authored-By: debadair <[email protected]> * [DOCS] Incorporated feedback from lcawl. * [DOCS] Fixes broken link * [DOCS] Removed tip about temporary superuser when upgrading the security index.
* [DOCS] First pass at 7.0 upgrade update. * [DOCS] Fixed formatting issues & flagged the Upgrade Assistant as xpack. * Update docs/en/install-upgrade/upgrading-stack.asciidoc Co-Authored-By: debadair <[email protected]> * [DOCS] Incorporated feedback from lcawl. * [DOCS] Fixes broken link * [DOCS] Removed tip about temporary superuser when upgrading the security index.
First pass at the upgrade changes for 7.0.