[DOCS] Add docs for restoring to new cluster #79683
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When restoring a snapshot to a new cluster, users may expect the cluster to not contain any conflicting indices or data streams. However, some features, such as the GeoIP processor, automatically create indices at startup. This adds a related procedure to the restore a snapshot tutorial. I plan to improve other documentation related to feature states in snapshots in a separate PR(s). Relates to #79675
|
Pinging @elastic/es-docs (Team:Docs) |
jrodewig
added
:Core/Infra/Core
elasticmachine
added
Team:Core/Infra
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
|
Pinging @elastic/es-distributed (Team:Distributed) |
gwbrown
approved these changes
Oct 26, 2021
Comment on lines
+83
to
+85
| By default, a restore request attempts to restore all indices and data streams | ||
| in a snapshot, including <<system-indices,system indices and system data | ||
| streams>>. In most cases, you only need to restore a specific index or data |
There was a problem hiding this comment.
This is true for 7.16, for 8.0 this will not be the case when we get to merging this PR: #79670
After we merge that, 8.0 will restore (in order of preference, so feature_states always wins:
- The indices owned by the features named in
feature_states - All system indices if
include_global_stateis true - No system indices otherwise
We can merge this PR as-is though, because this is correct for the current 8.0-SNAPSHOT builds, and update the docs in #79670.
There was a problem hiding this comment.
Thanks! And yeah -- #79670 will make these docs much simpler. Thanks for making those changes.
|
Thanks @gwbrown! |
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 26, 2021
When restoring a snapshot to a new cluster, users may expect the cluster to not contain any conflicting indices or data streams. However, some features, such as the GeoIP processor, automatically create indices at startup. This adds and updates related procedures in the restore a snapshot tutorial. I plan to improve other documentation related to feature states in snapshots in a separate PR(s). This PR also updates the restore snapshot API's example to include the `indices` and `feature_states` parameters. Relates to #79675
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When restoring a snapshot to a new cluster, users may expect the cluster
to not contain any conflicting indices or data streams. However, some
features, such as the GeoIP processor, automatically create indices at
startup.
This adds and updates related procedures in the restore a snapshot tutorial.
I plan to improve other documentation related to feature states in snapshots
in a separate PR(s).
This PR also updates the restore snapshot API's example to include
the
indicesandfeature_statesparameters.Relates to #79675
Preview
https://elasticsearch_79683.docs-preview.app.elstc.co/guide/en/elasticsearch/reference/master/snapshots-restore-snapshot.html