[YARN-3554] Default value for maximum nodemanager connect wait time is too high

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.8.0, 2.7.1, 2.6.2, 3.0.0-alpha1
• Labels: BB2015-05-RFC newbie
• Target Version/s: 2.7.1, 2.6.2
• Hadoop Flags: Reviewed
• Assignee: Naganarasimha G R Assign to me
• Reporter: Jason Darrell Lowe
• Created: 28/Apr/15 20:27
• Updated: 20/Feb/19 23:39
• Resolved: 08/May/15 13:55

Description

The default value for yarn.client.nodemanager-connect.max-wait-ms is 900000 msec or 15 minutes, which is way too high. The default container expiry time from the RM and the default task timeout in MapReduce are both only 10 minutes.

Issue Links

• is related to: YARN-3238 Connection timeouts to nodemanagers are retried at multiple levels
• is related to: HADOOP-11398 RetryUpToMaximumTimeWithFixedSleep needs to behave more accurately
• is related to: YARN-3518 default rm/am expire interval should not be smaller than default resourcemanager connect wait time