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 Thu, 29 Oct 2015 20:28:28 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.3.patch

Thanks [~djp] for review and proposal! 
have updated .3 patch which let {{createRetryPolicy}} take additional parameters of retryWaitTime
and retryInterval, and only use default conf if these two parameters if not set. I also create
a new function call of {{createRMProxy}} which take these two additional parameters. I didn't
overwrite the existing {{createRMProxy}} because otherwise I need to update many of the function's
Could you help review the latest patch? Thanks!

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

View raw message