[
https://issues.apache.org/jira/browse/YARN-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916057#comment-13916057
]
Zhijie Shen commented on YARN-1445:
-----------------------------------
Sorry for raising the new thought so late, but i think it may be more
acceptable by multiple stakeholders. Referring to the recently added new
internal state KILLING, which is mapped to a prior state before it, we may do
the same thing for FINISHING. So, instead of merging FINISHING to FINISHED, we
can merging FINISHING to a prior state as well. Then, FINISHED will always be a
real final state with diagnostics information ready.
One problem with this approach is that after unregistration succeeds, the
client will still see the application in a non-final state for a while, because
internally when an application is at FINISHING, client can already be notified
of unregistration success. What we can do is to postpone the unregistration
success notification until the application is at FINISHED. Then, when client
receives the notification, the application will always in a final state. Any
idea?
> 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, YARN-1445.3.patch,
> YARN-1445.4.patch, YARN-1445.5.patch, YARN-1445.5.patch, YARN-1445.6.patch
>
>
> Today, we will transmit both RMAppState.FINISHING and RMAppState.FINISHED to
> YarnApplicationState.FINISHED.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
