[
https://issues.apache.org/jira/browse/HADOOP-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HADOOP-8041:
--------------------------------
Attachment: hadoop-8041.txt
Attached patch fixes the issue.
I didn't edit unit tests since this is just a logging change, but I verified on
a cluster that when the second NN is active, FsShell commands no longer print
warnings. If I put both NNs in standby mode, I get warnings as it flip-flops
back and forth trying to find an active one.
> HA: log a warning when a failover is first attempted
> -----------------------------------------------------
>
> Key: HADOOP-8041
> URL: https://issues.apache.org/jira/browse/HADOOP-8041
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ha
> Affects Versions: HA Branch (HDFS-1623)
> Reporter: Eli Collins
> Assignee: Todd Lipcon
> Attachments: hadoop-8041.txt
>
>
> Currently we always warn for each client operation made to a NN we've failed
> over to:
> {noformat}
> hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs dfs -lsr /
> 12/02/08 17:43:04 WARN retry.RetryInvocationHandler: Exception while invoking
> getFileInfo of class
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB after 0
> fail over attempts. Trying to fail over immediately.
> {noformat}
> I'm going to remove this warning in HDFS-2918 since we shouldn't warn every
> time a client performs an operation, eg could be weeks after the failover.
> But we should eg log a warning eg the client first does a failover.
--
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
