[YARN-2355] MAX_APP_ATTEMPTS_ENV may no longer be a useful env var for a container

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha1
• Labels: newbie
• Hadoop Flags: Incompatible change
• Release Note: Removed consumption of the MAX_APP_ATTEMPTS_ENV environment variable
• Assignee: Darrell Taylor
• Reporter: Zhijie Shen
• Created: 25/Jul/14 03:18
• Updated: 24/Jan/17 22:09
• Resolved: 27/May/15 23:41

Description

After YARN-2074, YARN-614 and YARN-611, the application cannot judge whether it has the chance to try based on MAX_APP_ATTEMPTS_ENV alone. We should be able to notify the application of the up-to-date remaining retry quota.

Issue Links

• is related to: TEZ-3253 Remove special handling for last app attempt (absence of ApplicationConstants.MAX_APP_ATTEMPTS_ENV in AM env)
• relates to: YARN-611 Add an AM retry count reset window to YARN RM
• relates to: YARN-2074 Preemption of AM containers shouldn't count towards AM failures
• relates to: YARN-614 Separate AM failures from hardware failure or YARN error and do not count them to AM retry count