[
https://issues.apache.org/jira/browse/HADOOP-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated HADOOP-4364:
-------------------------------------
Labels: newbie (was: )
> IPC.Client.handleConnectionFailure should bail out if the retry count is >=
> the maximum, not ==
> -----------------------------------------------------------------------------------------------
>
> Key: HADOOP-4364
> URL: https://issues.apache.org/jira/browse/HADOOP-4364
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.20.0
> Reporter: Steve Loughran
> Priority: Minor
> Labels: newbie
>
> Looking at the code in IPC.Client.handleConnectionFailure(), its clear that
> the connection setup exits if the client retrys equals the maximum specified
> if (curRetries == maxRetries) {
> throw ioe;
> }
> But there's nothing to stop anyone setting ipc.client.connect.max.retries=0
> in the configuration, and if that happens, the code will spin until the
> (integer) retry count wraps around. The test should be curRetries >=
> maxRetries
--
This message was sent by Atlassian JIRA
(v6.2#6252)
