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/03/01 23:23:13 UTC

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

Sandy Ryza created YARN-444:
-------------------------------

             Summary: 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