hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3518) default rm/am expire interval should not less than default resourcemanager connect wait time
Date Sat, 25 Apr 2015 13:42:38 GMT

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

sandflee updated YARN-3518:
---------------------------
    Summary: default rm/am expire interval should not less than default resourcemanager connect
wait time  (was: default rm/am expire interval should less than default resourcemanager connect
wait time)

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

Mime
View raw message