[YARN-3518] default rm/am expire interval should not be smaller than default resourcemanager connect wait time

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Component/s: client
• Labels: oct16-easy
• Assignee: sandflee
• Reporter: sandflee
• Created: 21/Apr/15 09:10
• Updated: 27/Oct/16 18:47

Description

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;

Issue Links

• relates to: YARN-3554 Default value for maximum nodemanager connect wait time is too high