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

Hudson commented on HADOOP-10657:
---------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #586 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/586/])
HADOOP-10657. Have RetryInvocationHandler log failover attempt at INFO level. 
Contributed by Ming Ma. (jing9: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1602941)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/RetryInvocationHandler.java


> Have RetryInvocationHandler log failover attempt at INFO level
> --------------------------------------------------------------
>
>                 Key: HADOOP-10657
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10657
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>             Fix For: 2.5.0
>
>         Attachments: HADOOP-10657-2.patch, HADOOP-10657.patch
>
>
> RetryInovcationHandler uses worthLogging flag to decide if it will do 
> logging. worthLogging will be false for first fails over given 
> invocationFailoverCount is zero. That addresses the log noise where the 
> second-listed NN is active.
> For other failover scenarios, it will be useful to log the error message at 
> info level for analysis purpose.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to