[
https://issues.apache.org/jira/browse/HADOOP-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785569#comment-13785569
]
Daryn Sharp commented on HADOOP-10015:
--------------------------------------
Would you please add an attachment with the stack trace? I don't believe you
should see the issue described unless you are explicitly executing within a
doAs and not catching exceptions. The logging was added back in the .20 days
(by me) because it can be exceedingly hard to debug security issues. On a
number of occasions, we had no idea kerberos/authentication/etc errors were
occurring because something was gobbling the exceptions and/or going into a
retry loop and appeared hung. Not logging IOExceptions effectively renders the
logging useless because everything interesting (security related) is an
IOException.
> UserGroupInformation prints out excessive ERROR warnings
> --------------------------------------------------------
>
> Key: HADOOP-10015
> URL: https://issues.apache.org/jira/browse/HADOOP-10015
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Attachments: HADOOP-10015.000.patch
>
>
> In UserGroupInformation::doAs(), it prints out a log at ERROR level whenever
> it catches an exception.
> However, in some cases IOExceptions are expected -- For example, the upp
> (e.g., calling exists() in filesystem). As a result, these error logs are
> benign but they are printed at the ERROR level, which confuses the operators.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
