hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API
Date Tue, 02 Apr 2013 07:21:15 GMT

    [ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619584#comment-13619584
] 

Bikas Saha commented on YARN-444:
---------------------------------

IMO when the container exits because YARN took some specific action on it eg. killed due to
preemption or killed due to memory then YARN should assign action specific exit status using
new values defined inside ContainerExitStatus. Currently, NM kills the container and assigns
its real exit code to exit status. So at the AM its hard to tell why the container exited.
Of course, not as part of this jira.
                
> 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: Sub-task
>          Components: api, applications/distributed-shell
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>         Attachments: YARN-444-1.patch, YARN-444.patch
>
>
> 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

Mime
View raw message