[
https://issues.apache.org/jira/browse/HDFS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282023#comment-13282023
]
Philip Zeyliger commented on HDFS-3447:
---------------------------------------
In a failed over situation, even at 'info' level this will end up with one log
message per client when there's a failover (which might be a reasonable steady
state case, since there's no reason to prefer A over B), which seems like a
lot. You might tone it down to DEBUG even.
> 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
> Priority: Minor
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
