hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Liochon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10015) UserGroupInformation prints out excessive ERROR warnings
Date Sun, 23 Mar 2014 15:28:51 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nicolas Liochon updated HADOOP-10015:
-------------------------------------

    Attachment: 10015.v6.patch

> UserGroupInformation prints out excessive ERROR warnings
> --------------------------------------------------------
>
>                 Key: HADOOP-10015
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10015
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Haohui Mai
>            Assignee: Nicolas Liochon
>             Fix For: 3.0.0, 2.3.0, 2.4.0
>
>         Attachments: 10015.v3.patch, 10015.v4.patch, 10015.v5.patch, 10015.v6.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)

Mime
View raw message