[
https://issues.apache.org/jira/browse/YARN-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834089#comment-13834089
]
Xuan Gong commented on YARN-1445:
---------------------------------
[~jlowe] The diagnostic issue may be not a good example. Sorry for the
confusing.
As I mentioned in my previous comment, AM sent out
unregisterApplicationMaster, it does not mean that AM is finished. (In MR case,
or DS case, after AM sent out the unregisterApplicationMaster, it does mean the
application is finished, because after that, AM will do nothing but exist). But
it may not be the case for the other applications, (AM might do other things,
such as monitoring, writing log, etc, after that). So, merging the finishing
state and finished state might be not a good idea. Because the client will not
known when the application is really finished.
Hopefully, this can explain why we want to separate the FINISHING and FINISHED
state.
[~zjshen] Please add the comment if you have better explanation. Thanks
> Separate FINISHING and FINISHED state in YarnApplicationState
> -------------------------------------------------------------
>
> Key: YARN-1445
> URL: https://issues.apache.org/jira/browse/YARN-1445
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Attachments: YARN-1445.1.patch, YARN-1445.2.patch
>
>
> Today, we will transmit both RMAppState.FINISHING and RMAppState.FINISHED to
> YarnApplicationState.FINISHED.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
