-
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-11670. Add CallerContext in NodeManager #6688
Conversation
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.
+1 LGTM, pending CI
💔 -1 overall
This message was automatically generated. |
@dineshchitlangia Thank you very much for your review. In my test environment, when running MR jobs, some of the HDFS-audit logs are as follows:
|
@dineshchitlangia Can you help review this pr again? Thank you very much! |
@yangjiandan can you please address the new check style violation? |
💔 -1 overall
This message was automatically generated. |
@dineshchitlangia @slfan1989 Thank you for your review. The style issue has been addressed and corrected. Could you please take another look? |
LGTM. |
Thank you, @slfan1989 and @dineshchitlangia, for reviewing my merge request and for your approval. I appreciate your time and feedback. |
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.
+1 LGTM
Thanks @yangjiandan for contribution and @whbing & @slfan1989 for your reviews. |
Description of PR
Currently, MR and Spark have added caller context, enabling tracing of HDFS/ResourceManager operators from Spark apps and MapReduce apps. However, operators from NodeManagers cannot be identified in the audit log. For example, HDFS operations issued from NodeManagers during resource localization cannot be identified.
How was this patch tested?
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?