[
https://issues.apache.org/jira/browse/MAPREDUCE-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786436#comment-13786436
]
Zhijie Shen commented on MAPREDUCE-5562:
----------------------------------------
bq. Could you elaborate on what those race conditions are and how this fixes it?
We've faced some race conditions, e.g. staging file being unexpected cleaned
such that the next AM attempt fails (and previous jiras we fixed), which are
caused by the unregister exception is captured and ignored. What I'm worrying
about is that there're more race conditions that we're still not aware of.
Again, i agree exit at the unregister exception is not perfect fix, but it can
prevent that the race conditions unregister() fails while the following work is
still running without being aware of unregister() failure.
> MR AM should exit when unregister() throws exception
> ----------------------------------------------------
>
> Key: MAPREDUCE-5562
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5562
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Attachments: MAPREDUCE-5562.1.patch, MAPREDUCE-5562.2.patch,
> MAPREDUCE-5562.3.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
