hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1445) Separate FINISHING and FINISHED state in YarnApplicationState
Date Tue, 04 Mar 2014 14:37:24 GMT

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

Jason Lowe commented on YARN-1445:
----------------------------------

bq. Then, it is possible that AM is unregistered, and RM tells the client that the application
is still running. When the client moves on to contact AM, AM has proceeded and exited before
being able to respond the client request.

This race will always exist and is inherent with asynchronous processes.  The client could
check the RM and the app could really be RUNNING, but by the time the client gets around to
contacting the app the AM has rushed through the FINISHING and FINISHED state and could be
gone by the time the client gets there.  That's why ClientServiceDelegate retries on errors
and re-evaluates whether to go to the AM or history server on each retry.



> 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.2#6252)

Mime
View raw message