[YARN-444] Move special container exit codes from YarnConfiguration to API

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.3-alpha
• Fix Version/s: 2.1.0-beta
• Component/s: api, applications/distributed-shell
• Hadoop Flags: Reviewed
• Assignee: Sandy Ryza
• Reporter: Sandy Ryza
• Created: 01/Mar/13 22:22
• Updated: 27/Aug/13 22:15
• Resolved: 15/Apr/13 23:55

Description

YarnConfiguration currently contains the special container exit codes INVALID_CONTAINER_EXIT_STATUS = -1000, ABORTED_CONTAINER_EXIT_STATUS = -100, and DISKS_FAILED = -101.

These are not really not really related to configuration, and YarnConfiguration should not become a place to put miscellaneous constants.

Per discussion on YARN-417, appmaster writers need to be able to provide special handling for them, so it might make sense to move these to their own user-facing class.

Issue Links

• relates to: YARN-417 Create AMRMClient wrapper that provides asynchronous callbacks
• relates to: MAPREDUCE-5151 Update MR App after YARN-444