You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hitesh Shah (Commented) (JIRA)" <ji...@apache.org> on 2011/11/15 22:45:52 UTC
[jira] [Commented] (MAPREDUCE-3027) MR-279: Completed container
exit state needs to be enhanced to differentiate between container
aborts/failures and actual application process exit codes
[ https://issues.apache.org/jira/browse/MAPREDUCE-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150798#comment-13150798 ]
Hitesh Shah commented on MAPREDUCE-3027:
----------------------------------------
Both unix and windows use positive range exit status values. ( unix 0-255, windows uses signed 32-bit int but used range seems to be 0-15000+). Therefore, given that we use an int, we are quite safe for now.
The literals in ContainerStatus are there as using the actual variable name will require creating a dependency on yarn-common from yarn-api and that will create a cyclic dependency. Leaving the literal as is for now and just closing out this jira as invalid.
> MR-279: Completed container exit state needs to be enhanced to differentiate between container aborts/failures and actual application process exit codes
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3027
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3027
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Fix For: 0.24.0
>
>
> Currently, a completed container's exit status is set to -100 to denote the container being killed by the framework either as a result of the application releasing the container or a node failure. An application process may also return an exit code of -100 creating an ambiguity.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira