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

Hudson commented on HADOOP-17116:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #18430 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/18430/])
HADOOP-17116. Skip Retry INFO logging on first failover from a proxy 
(hanishakoneru: rev e62d8f841275ee47a0ba911415aac9e39af291c6)
* (edit) 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/RetryInvocationHandler.java


> Skip Retry INFO logging on first failover from a proxy
> ------------------------------------------------------
>
>                 Key: HADOOP-17116
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17116
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ha
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>         Attachments: HADOOP-17116.001.patch, HADOOP-17116.002.patch, 
> HADOOP-17116.003.patch
>
>
> RetryInvocationHandler logs an INFO level message on every failover except 
> the first. This used to be ideal before when there were only 2 proxies in the 
> FailoverProxyProvider. But if there are more than 2 proxies (as is possible 
> with 3 or more NNs in HA), then there could be more than one failover to find 
> the currently active proxy.
> To avoid creating noise in clients logs/ console, RetryInvocationHandler 
> should skip logging once for each proxy.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to