[jira] [Updated] (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:all-tabpanel ] Bikas Saha updated YARN-444: Issue Type: Sub-task (was: Improvement) Parent: YARN-386 > 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 > > 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
[jira] [Updated] (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:all-tabpanel ] Sandy Ryza updated YARN-444: Attachment: YARN-444.patch > 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
[jira] [Updated] (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:all-tabpanel ] Sandy Ryza updated YARN-444: Attachment: YARN-444-1.patch > 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
[jira] [Updated] (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:all-tabpanel ] Sandy Ryza updated YARN-444: Attachment: YARN-444-2.patch > 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-2.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
[jira] [Updated] (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:all-tabpanel ] Sandy Ryza updated YARN-444: Attachment: YARN-444-2.patch > 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-2.patch, YARN-444-2.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
[jira] [Updated] (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:all-tabpanel ] Sandy Ryza updated YARN-444: Attachment: YARN-444-2.patch > 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-2.patch, YARN-444-2.patch, > YARN-444-2.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
