hadoop-yarn-issues mailing list archives

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

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

Sandy Ryza commented on YARN-444:
---------------------------------

bq. As a logic extension of this, I think we should convert the ExitStatus into an object
which holds...

What would be the use of the meaning/description? ContainerStatus already contains a diagnostic
string that in theory should be holding the same information, right?

Uploading a patch that adds the annotations to ContainerExitStatus, removes the references
to specific literals, and adds an enum to yarn_protos.
                
> 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