[
https://issues.apache.org/jira/browse/MAPREDUCE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915246#comment-13915246
]
Jason Lowe commented on MAPREDUCE-5547:
---------------------------------------
bq. We previously observe the case that RM is restarting, such that the MR job
fails at unregistration, it then starts the second attempt, and is running. On
the other side, JHS has already show the job is finished successfully.
Yes, the states can get out of sync, but does this actually break anything
(e.g.: Oozie, Pig, something that will do something bad based on that
out-of-sync state)? As Bobby mentioned with the _SUCCESS file and other
out-of-band client notifications, we have this problem today and cannot solve
it completely.
> Job history should not be flushed to JHS until AM gets unregistered
> -------------------------------------------------------------------
>
> Key: MAPREDUCE-5547
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5547
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Attachments: MAPREDUCE-5547.1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
