[ https://issues.apache.org/jira/browse/YARN-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated YARN-3518: ------------------------------------------ Labels: oct16-easy (was: BB2015-05-TBR configuration newbie) Component/s: (was: nodemanager) (was: resourcemanager) client > 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: client > Reporter: sandflee > Assignee: sandflee > Labels: oct16-easy > Attachments: YARN-3518.001.patch, YARN-3518.002.patch, > YARN-3518.003.patch, YARN-3518.004.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) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org