[
https://issues.apache.org/jira/browse/HADOOP-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788829#comment-13788829
]
Hadoop QA commented on HADOOP-10015:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12607265/HADOOP-10015.002.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3191//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3191//console
This message is automatically generated.
> 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, 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.1#6144)
