Comments (5)
I'm still investigating whether my statement above regarding restoring snapshots to 6.x is completely correct.
Here is an additional note: "if in 5.x you got rid off all 2.x indices and all your internal indices were created in 5.x it is possible to upgrade to 6.x without upgrading the indices first. However, security is not going to work until you upgrade the .security index and watcher is not going to work until you upgrade the .watches index."
We'll also need to update the language on this page: https://www.elastic.co/guide/en/elasticsearch/reference/master/modules-snapshots.html
“A snapshot of an index created in 2.x can be restored to 5.x.
A snapshot of an index created in 1.x can be restored to 2.x.
A snapshot of an index created in 1.x can not be restored to 5.x.”
from stack-docs.
Strictly speaking, it's not a requirement to create a new repo / reindex every time you move major versions (I could have started off on 5.0, snapshotted through the major, and upgraded to 6.0 and we'd still be perfectly fine reading the old snapshot), but it is generally a best practice when possible. Also, you could create a snapshot repository in 5.0 that contains an index that was created in 2.x and that would be unrestorable once you move to 6.0. I think we should strive to convey a few warnings and best practices:
Indices that were created in 2.x are unreadable in 6.x.
I think we do a good job of conveying this already.Snapshots are incremental and may contain multiple indices that were created on various versions of Elasticsearch. This means if any of the indices in the snapshot were created prior to 5.0 (the "initial" bit before the incremental bits on top of it), they'll need to be reindex into a new snapshot repository in order to be restorable in 6.x
. I think a warning like this could go in both the snapshot/restore docs and in the stack upgrade docs.It's best practice to create a new snapshot repository for each major version.
I don't think we have this anywhere, and I'd be in favor of it being in the snapshot/restore docs.
As an aside, our snapshot/restore is hugely valuable but the semantics are pretty challenging and we'll need to address that over time. Having to write this type of documentation is challenging at best and that's generally a sign of a difficult-to-use feature.
from stack-docs.
from stack-docs.
We want to more or less completely revisit how snapshot/restore works.
from stack-docs.
from stack-docs.
Related Issues (20)
- [ML] Anomaly detection alert screenshots are out of date HOT 2
- [DOCS] Add Elastic Security breaking changes to Installation and Upgrade Guide for 8.4
- [DOCS] SAML with Azure Active Directory using outdate API
- [DOCS] Add Elastic Security breaking changes to Installation and Upgrade Guide for 8.5
- [Docs] modify CSS to show "parser options" in italic in the Elastic Docs, similar to Github
- [DOCS] Glossary improvements
- Create an offline snapshot for air-gapped installation docs
- [DOCS] Add Elastic Security breaking changes to Installation and Upgrade Guide for 8.6
- Elastic Azure Links Redirect to ERROR URLs HOT 10
- [DOCS] Add Elastic Security breaking changes to Installation and Upgrade Guide for 8.7
- Enterprise Search is missing from upgrade steps
- [DOCS] Add Elastic Security breaking changes to Installation and Upgrade Guide for 8.8
- [DOCS] Update security breaking changes link from 8.8.0 to 8.8.1
- List ports and routes required for Stack deployment HOT 10
- [DOCS] Update security breaking changes link from 8.8.1 to 8.8.2
- [DOCS] Update security breaking changes link from 8.8.2 to 8.9.0
- Add ECE to air-gapped install docs HOT 1
- [BUG] Update broken links, job IDs in pre-built ML job reference docs
- [ML] Clarify E5 built-in NLP model offline installation HOT 3
- Broken links to AD jobs
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from stack-docs.