You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2015/11/24 23:33:11 UTC

[jira] [Updated] (YARN-4132) Separate configs for nodemanager to resourcemanager connection timeout and retries

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

Jason Lowe updated YARN-4132:
-----------------------------
    Hadoop Flags: Reviewed
         Summary: Separate configs for nodemanager to resourcemanager connection timeout and retries  (was: Nodemanagers should try harder to connect to the RM)

> Separate configs for nodemanager to resourcemanager connection timeout and retries
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-4132
>                 URL: https://issues.apache.org/jira/browse/YARN-4132
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>            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.6.2.patch, YARN-4132.6.patch, YARN-4132.7.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)