[
https://issues.apache.org/jira/browse/MAPREDUCE-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786408#comment-13786408
]
Jason Lowe commented on MAPREDUCE-5562:
---------------------------------------
bq. Now, I'm trying to be so harsh to the unregister exceptions is try to avoid
the race conditions that we found recently or are still unseen as much as
possible, unblocking release 2.2.0.
Could you elaborate on what those race conditions are and how this fixes it?
bq. Yes, it's not good, but even if unregister() succeeds, the staging
directory will be likely not to be cleaned due to some other failure in between.
How is the likelihood of cleaning the staging directory successfully related to
communicting with the RM? It doesn't contact the RM to clean the staging
directory. If the AM is the last attempt, it should do what it can to exit
normally despite the 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)
