Updates "Reading indices from older Elasticsearch versions" topic #919
Conversation
...oy-manage/upgrade/deployment-or-cluster/reading-indices-from-older-elasticsearch-versions.md
Outdated
Show resolved
Hide resolved
...oy-manage/upgrade/deployment-or-cluster/reading-indices-from-older-elasticsearch-versions.md
Outdated
Show resolved
Hide resolved
|
|
||
| In the future, we plan on streamlining the upgrade process going forward, making it easier to take legacy indices along when going to future major {{es}} versions. | ||
| 1. Take a snapshot of the indices in the old cluster. | ||
| 2. Delete any indices created before 8.0.0. |
There was a problem hiding this comment.
I get confused about which ES version we are now covering. If it's about upgrading from 5.x or 6.x, the instructions don't change in 9.0 compared to before? I think that this 8.0.0 should actually still be 7.0.0. Does that make sense?
There was a problem hiding this comment.
That depends probably if you need to write to the index or not. 7.0 indices won't block the upgrade if in read-only mode so maybe we could expand this to describe this or link to relevant docs elsewhere?
There was a problem hiding this comment.
that yes, but I think the version that was incremented from 7.0 to 8.0 per-se is wrong?
| 2. Delete any indices created before 8.0.0. | ||
| 3. Upgrade the cluster without the old indices, then [restore](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-restore) the legacy indices from the snapshot or [mount](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-searchable-snapshots-mount) them using searchable snapshots. | ||
|
|
||
| % In the future, we plan on streamlining the upgrade process going forward, making it easier to take legacy indices along when going to future major {{es}} versions. |
There was a problem hiding this comment.
This last note no longer makes sense, isn't that what we have done with 9.0, meaning that you can bring along indices that were previously archived in 8.x (from 5.x or 6.x), as well as mark 7.x indices read-only and take them with you ? @cbuescher does that make sense to you?
There was a problem hiding this comment.
"take legacy indices along when going to future major {{es}} versions"
I think this statement is ambiguous, like e.g. I could mean being able to write to legacy indices as well. We know that's not what it means or will probably ever mean but I think the intention when this was added was to say we will keep improving this. I'm not sure we need to keep this around, but I also don't think we've reached with with v9 yet, e.g. you cannot simply keep version 5/6 indices through an upgrade without remounting a snapshot as far as I know. Or am I wrong here?
There was a problem hiding this comment.
you cannot simply keep version 5/6 indices through an upgrade without remounting a snapshot as far as I know
yes you can!
There was a problem hiding this comment.
Then lets scratch that last note here, it that what you suggest?
There was a problem hiding this comment.
yes that's what I'd suggest, if you agree :)
4 participants
Preview here.
Contributes to https://github.com/elastic/docs-projects/issues/247 and https://github.com/elastic/docs-projects/issues/270. Updates this topic to be compatible with 9.0.
Asciidoc version for 8.x: https://www.elastic.co/guide/en/elasticsearch/reference/current/archive-indices.html.