hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10127) Add ipc.client.connect.retry.interval to control the frequency of connection retries
Date Fri, 29 Nov 2013 06:55:36 GMT

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

Karthik Kambatla commented on HADOOP-10127:

[~sandyr] and [~stevel], thanks for the discussion. Agree with you both on how to handle this.

I propose the following:
# Add ipc.client.connect.retry.interval in this JIRA, so the knob is available to be played
with in YARN.
# YARN-1028 would implement ConfiguredFailoverProxyProvider with the not-so-nice 10 second
delay to failover for all entities connecting to the RM.
# YARN-1460 to define yarn-specific ipc-client configs that the clients use, and add an exponential
backoff and jitter at least for NM -> RM.

With that plan, what do you think of the current patch? 

> Add ipc.client.connect.retry.interval to control the frequency of connection retries
> ------------------------------------------------------------------------------------
>                 Key: HADOOP-10127
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10127
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 2.2.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: hadoop-10127-1.patch
> Currently, {{ipc.Client}} client attempts to connect to the server every 1 second. It
would be nice to make this configurable to be able to connect more/less frequently. Changing
the number of retries alone is not granular enough.

This message was sent by Atlassian JIRA

View raw message