hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3457) IPC.Client retry delay could be made configurable
Date Thu, 24 Dec 2009 12:24:29 GMT

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

Steve Loughran commented on HADOOP-3457:
----------------------------------------

At the very least, the interrupt should fail the thread, otherwise client code can't easily
halt threads trying to talk to servers that aren't there. 

Testing: not easy. 

> 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.18.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> 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.


Mime
View raw message