hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mayank Bansal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures
Date Thu, 26 Jun 2014 00:49:24 GMT

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

Mayank Bansal commented on MAPREDUCE-5900:
------------------------------------------

Hi Wangda,

I dont think we can add checkpointing as of now. I think we don't need TA_PREEMTION transition
as of now and KILL is suffice. However when we add checkpointing then that patch will automatically
take care of that.

Thanks,
Mayank


> Container preemption interpreted as task failures and eventually job failures 
> ------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5900
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: applicationmaster, mr-am, mrv2
>    Affects Versions: 2.4.1
>            Reporter: Mayank Bansal
>            Assignee: Mayank Bansal
>         Attachments: MAPREDUCE-5900-1.patch, MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch,
MAPREDUCE-5900-trunk-2.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as a container
being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message