hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10015) UserGroupInformation prints out excessive ERROR warnings
Date Mon, 07 Oct 2013 23:36:44 GMT

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

Brandon Li updated HADOOP-10015:
--------------------------------

    Description: 
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.

  was:
In UserGroupInformation::doAs(), it prints out a log at ERROR level whenever it catches an
exception.

However, it prints benign warnings in the following paradigms:

{noformat}

{noformat}

in some cases IOExceptions are expected by the upper level users (e.g., FileSystem#exists()
in filesystem). As a result, these error logs are benign but they are printed at the ERROR
level, which confuses the operators.


> 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
>
>
> 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)

Mime
View raw message