-
Notifications
You must be signed in to change notification settings - Fork 8.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
YARN-11534. Fixed exception handling when container signalling is interrupted #5864
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
…errupted Change-Id: I5cc10436be452ee51c604acd60d92b49fa10a75b
💔 -1 overall
This message was automatically generated. |
Change-Id: I379f76d5c45f7371a81fb6a01bbb4f2807f27ef6
Change-Id: Idce41dfff72f0f209683a75b5743672446288f91
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
Change-Id: I4933b6102a3bd283206ce9980ad037e750eef4a7
@p-szucs thanks for the patch! The latest state looks good to me, let's wait for the new build result with the blanks fixed. |
Sure, thanks for the review @brumi1024! |
🎊 +1 overall
This message was automatically generated. |
Merged to trunk. |
jiajunmao
pushed a commit
to jiajunmao/hadoop-MLEC
that referenced
this pull request
Feb 6, 2024
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.
Change-Id: I5cc10436be452ee51c604acd60d92b49fa10a75b
Description of PR
Fixed exception handling when container signalling is interrupted. Issue details are in this ticket: https://issues.apache.org/jira/browse/YARN-11534
Previously in LinuxContainerExecutor we threw only IOException when an error occurred during signalling a container. In RecoveredContainerLaunch, where we are calling this method, we use an "interrupted" flag to determine if the container reacquisition was interrupted. In that case we won't persist the default LOST state in the NM state store.
This flag is only set when catching Interrupted and InterruptedIOExceptions during container recovery. For that reason we need to differentiate the cases when signalling is interrupted, and we can use the ContainerExecutionException's exit code for that.
How was this patch tested?
With unit tests.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?