[
https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591088#comment-13591088
]
Bikas Saha commented on YARN-444:
---------------------------------
I like the proposal to move them out of YARN configuration unless there was a
specific reason to put them there.
I would really like to not call these exit codes. It nice that the API is
ContainerStatus.*getExitStatus()*. Exit codes may be returned when the
container exits by itself without any action by YARN. When YARN takes an action
(such as pre-empt, abort, kill due to memory etc) then it can set a YARN
specific status to reflect that action. This status can be programmatically
used by clients (such as the app client mentioned in the description) to take
necessary action.
> Move special container exit codes from YarnConfiguration to API
> ---------------------------------------------------------------
>
> Key: YARN-444
> URL: https://issues.apache.org/jira/browse/YARN-444
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: api, applications/distributed-shell
> Affects Versions: 2.0.3-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
