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

sandflee commented on YARN-3518:
--------------------------------

agree, we should set nm, am, client  separately

> default rm/am expire interval should not less than default resourcemanager 
> connect wait time
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-3518
>                 URL: https://issues.apache.org/jira/browse/YARN-3518
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager, resourcemanager
>            Reporter: sandflee
>            Assignee: sandflee
>              Labels: configuration, newbie
>         Attachments: YARN-3518.001.patch
>
>
> take am for example, if am can't connect to RM, after am expire (600s), RM 
> relaunch am, and there will be two am at the same time util resourcemanager 
> connect max wait time(900s) passed.
> DEFAULT_RESOURCEMANAGER_CONNECT_MAX_WAIT_MS =  15 * 60 * 1000;
> DEFAULT_RM_AM_EXPIRY_INTERVAL_MS = 600000;
> DEFAULT_RM_NM_EXPIRY_INTERVAL_MS = 600000;



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

Reply via email to