hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chang Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4132) Nodemanagers should try harder to connect to the RM
Date Wed, 11 Nov 2015 15:05:11 GMT

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

Chang Li updated YARN-4132:
---------------------------
    Attachment: YARN-4132.5.patch

Thanks [~jlowe] for review! .5 patch only has one createRMProxy which takes two additional
inputs of retry time and retry interval. ServerRMProxy and ClientRMProxy pass those two inputs
according to different values in conf.
Conf naming is fixed. Test is also tuned down to around 4 seconds. 

> Nodemanagers should try harder to connect to the RM
> ---------------------------------------------------
>
>                 Key: YARN-4132
>                 URL: https://issues.apache.org/jira/browse/YARN-4132
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: YARN-4132.2.patch, YARN-4132.3.patch, YARN-4132.4.patch, YARN-4132.5.patch,
YARN-4132.patch
>
>
> Being part of the cluster, nodemanagers should try very hard (and possibly never give
up) to connect to a resourcemanager. Minimally we should have a separate config to set how
aggressively a nodemanager will connect to the RM separate from what clients will do.



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

Mime
View raw message