[
https://issues.apache.org/jira/browse/HADOOP-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-3457:
-----------------------------------
Attachment: HADOOP-3457.patch
This patch turns InterruptedException into InterruptedIOException, and so
propagates upstream. The underlying cause of the failure is retained as a
nested clause, in case whoever using the client library is curious as to why
the connection is failing.
> IPC.Client retry delay could be made configurable
> -------------------------------------------------
>
> Key: HADOOP-3457
> URL: https://issues.apache.org/jira/browse/HADOOP-3457
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.20.2, 0.21.0, 0.22.0
> Reporter: Steve Loughran
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: HADOOP-3457.patch
>
>
> The delay of ipc.Client.handleConnectionFailure() that causes the client to
> block and wait is hard coded at 1 second; any interruption of the thread is
> treated as a shortening of the delay.
> // otherwise back off and retry
> try {
> Thread.sleep(1000);
> } catch (InterruptedException ignored) {}
>
> 1. this delay could be configurable; different clients may wish to retry
> more/less often. or at a slightly different rate than their peers.
> 2. interrupting the thread may imply the client has been requested to
> terminate -this could be handled by declaring failure early, rather than
> continuing to retry until the retry count is exceeded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
