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 Mon, 08 Apr 2013 20:01:17 GMT

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

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

It seems like the code which is swallowing the exceptions should just be changed to log before
swallowing, rather than putting this generic log here. Perhaps we can introduce a new overload
of doAs() which takes a LOG object, for the places where we really want to log the exception
alongside the UGI string?

If we change it to DEBUG, you can still set up your log4j properties to enable this particular
class's DEBUG level without doing so everywhere.
                
> 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