[YARN-542] Change the default global AM max-attempts value to be not one

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0-beta
• Hadoop Flags: Reviewed
• Assignee: Zhijie Shen
• Reporter: Vinod Kumar Vavilapalli
• Created: 04/Apr/13 20:00
• Updated: 27/Aug/13 22:15
• Resolved: 20/Apr/13 00:36

Description

Today, the global AM max-attempts is set to 1 which is a bad choice. AM max-attempts accounts for both AM level failures as well as container crashes due to localization issue, lost nodes etc. To account for AM crashes due to problems that are not caused by user code, mainly lost nodes, we want to give AMs some retires.

I propose we change it to atleast two. Can change it to 4 to match other retry-configs.

Issue Links

• is related to: MAPREDUCE-5145 Change default max-attempts to be more than one for MR jobs as well
• relates to: YARN-378 ApplicationMaster retry times should be set by Client
• relates to: YARN-614 Separate AM failures from hardware failure or YARN error and do not count them to AM retry count