-
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
Make peer recovery send file chunks async #44468
Merged
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
dnhatn
added
>enhancement
:Distributed Indexing/Recovery
Anything around constructing a new shard, either from a local or a remote source.
v8.0.0
v7.4.0
labels
Jul 17, 2019
Pinging @elastic/es-distributed |
@ywelsch @original-brownbear Please review the additional commit: 738ab4e. |
ywelsch
approved these changes
Jul 17, 2019
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.
LGTM
Thanks Yannick. |
dnhatn
added a commit
that referenced
this pull request
Jul 18, 2019
dnhatn
added a commit
that referenced
this pull request
Oct 22, 2019
dnhatn
added a commit
that referenced
this pull request
Oct 22, 2019
This was referenced Feb 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/Recovery
Anything around constructing a new shard, either from a local or a remote source.
>enhancement
v7.4.0
v8.0.0-alpha1
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.
This PR reintroduces #44040 with an additional commit fixing the notify once assertion. We can call
MultiFileTransfer#onComplete
twice if the recovery is canceled during the clean_files step.Send_files step calls
MultiFileTransfer#onComplete(null)
to start the clean_files stepClean_files sends and receives a response before the method returns. The response notifies the phase 1 listener (either success or failure).
Before returning, the clean_files method checkForCancel and throws an exception as the recovery was canceled. This causes the send_files listener to notify the phase1 listener. However, the phase1 listener was notified in step 2 already. The phase1 listener must be notified at most once as it delegates to ListenerFuture.
The new commit allows StepListener to be notified multiple times.
Relates #44040
Relates #36195