-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HADOOP-18138. UserGroupInformation shouldn't log exception unnecessarily #4007
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
💔 -1 overall
This message was automatically generated. |
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.
I thought it was intentional, to log the stack trace of where it was being called?
I see. Didn't know the context. It's a bit confusing to see the stack trace like this though:
and it could makes people think there's something wrong in the
|
I'm wary of things that require us to reimplement the logging system handling the stack trace details. Maybe we could convey the purpose in either the exception message or the exception type instead? e.g. if (LOG.isDebugEnabled()) {
LOG.debug("PrivilegedAction [as: {}][action: {}]", this, action,
new JustForDebuggingException("call stack for privileged action; not an indication of a failure"));
} |
Description of PR
In UserGroupInformation.doAs, we currently create a new Exception and log it in LOG.debug. This doesn't look necessary:
How was this patch tested?
Existing tests.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?