[
https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771192#comment-13771192
]
Jian He commented on MAPREDUCE-5505:
------------------------------------
One more issue is that we may need better exception handling in
RMCommunicator.unregister. Now, it's simply ignoring any exceptions coming out
of finishApplicationMaster. It can be the case that finishApplicationMaster
throws exception before unregister event is sent out. Since MR is ignoring
exceptions, JobClient will see SUCCEEDED, but on RM side, since unregister
event is not received,RMApp stays on running and eventually failed.
> Clients should be notified job finished only after job successfully
> unregistered
> ---------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5505
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5505
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Jian He
> Assignee: Zhijie Shen
> Attachments: MAPREDUCE-5505.1.patch, MAPREDUCE-5505.1.patch
>
>
> This is to make sure user is notified job finished after job is really done.
> This does increase client latency but can reduce some races during unregister
> like YARN-540
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
