You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/04/01 19:17:15 UTC

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

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

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

My thinking behind the plurals was that using the singular makes it seems like a ContainerExitStatus is something that the class allows you to instantiate, where rather, in the manner of the Arrays or Collections classes, the class is more of a namespace for holding related static fields and methods.  What do you think?  I'll fix the comments when we decide which way to go.

                
> 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.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