You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2009/12/24 13:38:29 UTC

[jira] Assigned: (HADOOP-3457) IPC.Client retry delay could be made configurable

     [ https://issues.apache.org/jira/browse/HADOOP-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran reassigned HADOOP-3457:
--------------------------------------

    Assignee: Steve Loughran

> 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
>            Assignee: 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.