[
https://issues.apache.org/jira/browse/HADOOP-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204697#comment-13204697
]
Aaron T. Myers commented on HADOOP-8041:
----------------------------------------
I agree with Todd's analysis. If a given failover proxy has never successfully
made a call to the first NN it tries, no reason to print any info. If after
having been successfully connected to an NN we then perform a client failover,
that seems like info worth sharing with the user.
+1, the patch looks good to me.
> 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
> failedover 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-2922 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 when the client first does a failover so it
> shows up eg in the MR and HBase logs.
--
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
