hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1445) Separate FINISHING and FINISHED state in YarnApplicationState
Date Wed, 27 Nov 2013 06:38:35 GMT

    [ https://issues.apache.org/jira/browse/YARN-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833522#comment-13833522

Xuan Gong commented on YARN-1445:

Let me give more details:
AM sends unregisterApplicationMaster event with the diagnostic message. When the RMAppAttempt
receives this event, and send the RMAppAttemptEventType.UNREGISTERE to RMApp, and RMApp will
go to finishing state. At this time, the yarnapplicationstate will become finished. But at
this time, the diagnostic message which is from AM is still at RMAppAttempt until RMAppAttempt
send the RMAppFinishedAttemptEvent to RMApp. So, before this, at the client side, when the
client sees the YarnApplicationState become finished, the client will consider this application
is finished, but at this time, he can not get any diagnostic message until this application
is really finished (RMApp is at Finished state).

My use case is Distributed Shell. We can not find any diagnostic message at the console (At
this time, RMApp is at Finishing state, and YarnApplicationState is finished state).

> 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
> Today, we will transmit both RMAppState.FINISHING and RMAppState.FINISHED to YarnApplicationState.FINISHED.

This message was sent by Atlassian JIRA

View raw message