[
https://issues.apache.org/jira/browse/HADOOP-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942255#comment-13942255
]
Nicolas Liochon commented on HADOOP-10015:
------------------------------------------
bq. I'll hesitantly reverse course and say just make it a debug. Much cleaner
than a bunch of conditionals on exceptions.
I'm ok with that.
bq. Since the related fix has landed trunk a while ago, maybe it is better to
file a separate jira to discuss further improvement?
I hope that changing a an error/warn log to debug will not require too much
discussion, but if you really want it I can create a new jira.
> 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: Nicolas Liochon
> Attachments: 10015.v3.patch, 10015.v4.patch, HADOOP-10015.000.patch,
> HADOOP-10015.001.patch, HADOOP-10015.002.patch
>
>
> In UserGroupInformation::doAs(), it prints out a log at ERROR level whenever
> it catches an exception.
> However, it prints benign warnings in the following paradigm:
> {noformat}
> try {
> ugi.doAs(new PrivilegedExceptionAction<FileStatus>() {
> @Override
> public FileStatus run() throws Exception {
> return fs.getFileStatus(nonExist);
> }
> });
> } catch (FileNotFoundException e) {
> }
> {noformat}
> For example, FileSystem#exists() follows this paradigm. Distcp uses this
> paradigm too. The exception is expected therefore there should be no ERROR
> logs printed in the namenode logs.
> Currently, the user quickly finds out that the namenode log is quickly filled
> by _benign_ ERROR logs when he or she runs distcp in secure set up. This
> behavior confuses the operators.
> This jira proposes to move the log to DEBUG level.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
