-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
SNAPSHOT: Improve Resilience SnapshotShardService #36113
Merged
original-brownbear
merged 3 commits into
elastic:master
from
original-brownbear:minimal-fix-snapshot-stability
Dec 3, 2018
Merged
SNAPSHOT: Improve Resilience SnapshotShardService #36113
original-brownbear
merged 3 commits into
elastic:master
from
original-brownbear:minimal-fix-snapshot-stability
Dec 3, 2018
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
* Resolve the index in the snapshotting thread * Added test for routing table - snapshot state mismatch
original-brownbear
added
>bug
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
v7.0.0
v6.6.0
labels
Nov 30, 2018
Pinging @elastic/es-distributed |
ywelsch
approved these changes
Dec 3, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, let's do this (and also backport to 6.5).
executor.execute(new AbstractRunnable() { | ||
|
||
final SetOnce<Exception> failure = new SetOnce<>(); | ||
|
||
@Override | ||
public void doRun() { | ||
final IndexShard indexShard = indicesService.indexServiceSafe(shardId.getIndex()).getShardOrNull(shardId.id()); | ||
final IndexId indexId = indicesMap.get(shardId.getIndexName()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this can and should still be resolved outside the executor.
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this pull request
Dec 3, 2018
* Resolve the index in the snapshotting thread * Added test for routing table - snapshot state mismatch
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this pull request
Dec 3, 2018
* Resolve the index in the snapshotting thread * Added test for routing table - snapshot state mismatch
original-brownbear
added a commit
that referenced
this pull request
Dec 3, 2018
original-brownbear
added a commit
that referenced
this pull request
Dec 3, 2018
This was referenced Jan 15, 2019
kovrus
added a commit
to crate/crate
that referenced
this pull request
Apr 24, 2019
- Fix two races condition that lead to stuck snapshots (elastic/elasticsearch#37686) - Improve resilience SnapshotShardService (elastic/elasticsearch#36113) - Fix concurrent snapshot ending and stabilize snapshot finalization (elastic/elasticsearch#38368)
5 tasks
kovrus
added a commit
to crate/crate
that referenced
this pull request
Apr 25, 2019
- Fix two races condition that lead to stuck snapshots (elastic/elasticsearch#37686) - Improve resilience SnapshotShardService (elastic/elasticsearch#36113) - Fix concurrent snapshot ending and stabilize snapshot finalization (elastic/elasticsearch#38368)
kovrus
added a commit
to crate/crate
that referenced
this pull request
Apr 25, 2019
- Fix two races condition that lead to stuck snapshots (elastic/elasticsearch#37686) - Improve resilience SnapshotShardService (elastic/elasticsearch#36113) - Fix concurrent snapshot ending and stabilize snapshot finalization (elastic/elasticsearch#38368)
kovrus
added a commit
to crate/crate
that referenced
this pull request
Apr 25, 2019
- Fix two races condition that lead to stuck snapshots (elastic/elasticsearch#37686) - Improve resilience SnapshotShardService (elastic/elasticsearch#36113) - Fix concurrent snapshot ending and stabilize snapshot finalization (elastic/elasticsearch#38368)
kovrus
added a commit
to crate/crate
that referenced
this pull request
Apr 25, 2019
- Fix two races condition that lead to stuck snapshots (elastic/elasticsearch#37686) - Improve resilience SnapshotShardService (elastic/elasticsearch#36113) - Fix concurrent snapshot ending and stabilize snapshot finalization (elastic/elasticsearch#38368)
kovrus
added a commit
to crate/crate
that referenced
this pull request
Apr 26, 2019
- Fix two races condition that lead to stuck snapshots (elastic/elasticsearch#37686) - Improve resilience SnapshotShardService (elastic/elasticsearch#36113) - Fix concurrent snapshot ending and stabilize snapshot finalization (elastic/elasticsearch#38368)
mergify bot
pushed a commit
to crate/crate
that referenced
this pull request
Apr 26, 2019
- Fix two races condition that lead to stuck snapshots (elastic/elasticsearch#37686) - Improve resilience SnapshotShardService (elastic/elasticsearch#36113) - Fix concurrent snapshot ending and stabilize snapshot finalization (elastic/elasticsearch#38368)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
v6.5.3
v6.6.0
v7.0.0-beta1
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.
indexId
in the snapshot thread improves resilience in general because it covers any situations where the interaction withindicesService
runs into an exception but that exception is never reported to the master