[
https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006245#comment-14006245
]
Mayank Bansal commented on MAPREDUCE-5900:
------------------------------------------
Thanks [~jlowe] for the comments.
bq. Do the preemption diagnostics make it into the job history, or do they only
appear as long as the AM is active?
I verified and diagnostics info is going to job history files and very well
shown into the UI as well.
bq. One more issue is that we are targetting this jira for 2.4.1 and
MAPREDUCE-5848 depends on MAPREDUCE-5196 which is a very big patch for 2.4.1
I think we should still commit this JIRA in 2.4.1 and should target 5848( if
needed with TA_PREEMPTED even) with 5196 in major release.
Do you think we can do this for now ?
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
>
>
> 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)
