-
Notifications
You must be signed in to change notification settings - Fork 9.2k
YARN-11179. Show more detailed info when container token is expired #4437
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
Conversation
|
Minor improvement. Could u help review ? @dineshchitlangia @brumi1024 @9uapaw @slfan1989 @ashutoshcipher Thanks. |
|
@zuston Thank you for your contribution, I hope the following areas can be improved |
|
💔 -1 overall
This message was automatically generated. |
|
@slfan1989 Thanks your quick reply.
|
|
@zuston It seems that the plan is reasonable, can we also put the user information contained in the token in the messageBuilder? |
|
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
Description of PR
ISSUE: https://issues.apache.org/jira/browse/YARN-11179
I found in our nm logs, there is no appid in log about failing on starting containers when container token is expired. This will make hard to troubleshoot.
How was this patch tested?
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?