[
https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771212#comment-13771212
]
Zhijie Shen commented on MAPREDUCE-5505:
----------------------------------------
bq. JobClient will see SUCCEEDED, but on RM side, since unregister event is not
received,RMApp stays on running and eventually failed
JobClient won't see SUCCEEDED with the patch. Given exception is thrown by
finishApplicationMaster, markUnregistered will not be called, and JobClient
will still see RUNNING.
Anyway, +1 for better handling the exception from finishApplicationMaster.
Differentiate the handling of, for example, authorization and non-existence.
> 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
