Skip to content

[DOCS] Remove Outdated Snapshot Docs #61684

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 31, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -149,8 +149,8 @@ detailed insight into the current state of the recovery process by using <<indic
[discrete]
[[get-snapshot-stop-snapshot]]
=== Stop snapshot and restore operations
The snapshot and restore framework allows running only one snapshot or one restore operation at a time. If a currently
running snapshot was started by mistake, or takes unusually long, it can be stopped using the <<delete-snapshot-api,delete snapshot API>>.
To stop a currently running snapshot that was started by mistake or is taking unusually long, use
the <<delete-snapshot-api,delete snapshot API>>.
This operation checks whether the deleted snapshot is currently running. If it is, the delete snapshot operation stops
that snapshot before deleting the snapshot data from the repository.

Expand Down
3 changes: 1 addition & 2 deletions docs/reference/snapshot-restore/take-snapshot.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -80,8 +80,7 @@ Besides creating a copy of each data stream and index, the snapshot process can
cluster settings and templates. The transient settings and registered snapshot repositories are not stored as part of
the snapshot.

Only one snapshot process can be started in the cluster at any time. While a
snapshot of a particular shard is being
While a snapshot of a particular shard is being
created, this shard cannot be moved to another node, which can interfere with rebalancing and allocation
filtering. {es} can only move a shard to another node (according to the current allocation
filtering settings and rebalancing algorithm) after the snapshot process
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -194,9 +194,6 @@ private void cancelRemoved(SnapshotsInProgress snapshotsInProgress) {
}

private void startNewSnapshots(SnapshotsInProgress snapshotsInProgress) {
// For now we will be mostly dealing with a single snapshot at a time but might have multiple simultaneously running
// snapshots in the future
// Now go through all snapshots and update existing or create missing
final String localNodeId = clusterService.localNode().getId();
for (SnapshotsInProgress.Entry entry : snapshotsInProgress.entries()) {
final State entryState = entry.state();
Expand Down