hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3447) StandbyException should not be logged at ERROR level on server
Date Sat, 06 Apr 2013 00:01:22 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624211#comment-13624211
] 

Todd Lipcon commented on HDFS-3447:
-----------------------------------

This is actually difficult to fix because the logging is happening inside UserGroupInformation
instead of any IPC-specific place. It looks like UGI.doAs() will always log at ERROR level
any exception (added by HADOOP-7853).

[~daryn] -- do you think it's reasonable to drop that logging (UserGroupInformation.java:1493)
back to DEBUG level? I'd think that the UGI code should just pass through the exception, not
also be responsible for any logging. (the caller of doAs should do logging if it wants to)
                
> StandbyException should not be logged at ERROR level on server
> --------------------------------------------------------------
>
>                 Key: HDFS-3447
>                 URL: https://issues.apache.org/jira/browse/HDFS-3447
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.0.0-alpha
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>              Labels: newbie
>
> Currently, the standby NN will log StandbyExceptions at ERROR level any time a client
tries to connect to it. So, if the second NN in an HA pair is active, the first NN will spew
a lot of these errors in the log, as each client gets redirected to the proper NN. Instead,
this should be at INFO level, and should probably be logged in a less "scary" manner (eg "Received
READ request from client 1.2.3.4, but in Standby state. Redirecting client to other NameNode.")

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message