-
Notifications
You must be signed in to change notification settings - Fork 9.2k
YARN-11384: NPE in DelegationTokenRenewer causes all subsequent apps to fail with "Timer already cancelled" #7404
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
Conversation
This file contains hidden or 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
…to fail with "Timer already cancelled"
Member
Author
slfan1989
approved these changes
Feb 19, 2025
Contributor
|
@pan3793 LGTM. I need to research the deeper reasons behind this issue. |
|
💔 -1 overall
This message was automatically generated. |
Contributor
|
@pan3793 Thanks for the contribution! Merged into trunk. |
adideshpande
pushed a commit
to adideshpande/hadoop
that referenced
this pull request
Feb 27, 2025
…to fail with "Timer already cancelled" (apache#7404) Contributed by Cheng Pan. Reviewed-by: Shilun Fan <slfan1989@apache.org> Signed-off-by: Shilun Fan <slfan1989@apache.org>
YanivKunda
pushed a commit
to YanivKunda/hadoop
that referenced
this pull request
Mar 23, 2025
…to fail with "Timer already cancelled" (apache#7404) Contributed by Cheng Pan. Reviewed-by: Shilun Fan <slfan1989@apache.org> Signed-off-by: Shilun Fan <slfan1989@apache.org>
p-szucs
pushed a commit
to p-szucs/hadoop
that referenced
this pull request
Oct 22, 2025
…sequent apps to fail with "Timer already cancelled" (apache#612) YARN-11384: NPE in DelegationTokenRenewer causes all subsequent apps to fail with "Timer already cancelled" (apache#7404) Contributed by Cheng Pan. Reviewed-by: Shilun Fan <slfan1989@apache.org> Signed-off-by: Shilun Fan <slfan1989@apache.org> (cherry picked from commit 9c37baf25bf0e648435a54d195de595b2a577adc) Co-authored-by: Cheng Pan <chengpan@apache.org>
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.
Description of PR
As described in YARN-11384,
DelegationTokenRenewer#removeFailedDelegationTokenmay throw NPE due toappTokens.get(applicationId)returningnull(I'm not sure how this happened, but it does happen), such an uncaught exception stops the globalrenewalTimerand causes all subsequent apps to fail with "Timer already cancelled", this effectively leads the entire YARN cluster unavailable.This patch simply adds a null check to prevent the NPE.
How was this patch tested?
Change is straightforward I'm not sure whether it requires a UT with plenty of mocked stuff.
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?