hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishek Kapoor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4993) AM thinks it was killed when an error occurs setting up a task container launch context
Date Thu, 07 Mar 2013 06:36:13 GMT

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

Abhishek Kapoor commented on MAPREDUCE-4993:
--------------------------------------------

If the jar required for the job gets deleted in the middle while job is running, then job
should be failed and AM for the specific job should die, isn't it  a expected behaviour? 
If it is a expected then we can gracefully kill the AM with an appropriate diagnostics.

Please correct me if am wrong.

                
> AM thinks it was killed when an error occurs setting up a task container launch context
> ---------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4993
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4993
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>    Affects Versions: 2.0.3-alpha, 0.23.5
>            Reporter: Jason Lowe
>            Assignee: Abhishek Kapoor
>
> If an IOException occurs while setting up a container launch context for a task then
the AM exits with a KILLED status and no diagnostics.  The job should be marked as FAILED
(or maybe ERROR) with a useful diagnostics message indicating the nature of the error.

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