hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4243) Add retry on establishing Zookeeper conenction in EmbeddedElectorService#serviceInit
Date Thu, 22 Oct 2015 17:37:27 GMT

    [ https://issues.apache.org/jira/browse/YARN-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969519#comment-14969519
] 

Xuan Gong commented on YARN-4243:
---------------------------------

Thanks for the comments, [~kasha]

bq. To be consistent with the other config, can we call use zk-retries instead of zk.op.retries

Modified

bq. should we make the change to ActiveStandbyElector as a Common JIRA or at least create
a Common JIRA and close it as part of this one, so the common and HDFS devs are aware of this
change? They might want to update the way HDFS handles the retries situation as well.

Created https://issues.apache.org/jira/browse/HADOOP-12503, and link the ticket

> Add retry on establishing Zookeeper conenction in EmbeddedElectorService#serviceInit
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-4243
>                 URL: https://issues.apache.org/jira/browse/YARN-4243
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>         Attachments: YARN-4243.1.patch, YARN-4243.2.1.patch, YARN-4243.2.patch, YARN-4243.3.patch,
YARN-4243.4.patch, YARN-4243.5.patch
>
>
> Right now, the RM would shut down if the zk connection is down when the RM do the initialization.
We need to add retry on this part



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message