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 Mon, 25 Nov 2013 21:26:38 GMT

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

Jason Lowe commented on YARN-1445:

FINISHING means the app has unregistered and the RM is waiting for the application to exit
on its own.   FINISHED means the app is totally done and has exited.  I added the distinction
a while back because the RM was aggressively killing any application as soon as it unregistered,
leading to unclean shutdowns (e..g: failure to cleanup the staging directory).  See MAPREDUCE-4099
for details.  In hindsight I should have simply called the new state UNREGISTERED to help
avoid confusion, and my apologies for that.

I mapped the two RMApp states to a single YarnApplicationState since I didn't think clients
needed to know the distinction at the time and doing so meant breaking existing YARN clients
since they would now see a new, unrecognized state.  I'm assuming Xuan has a case where it's
necessary to distinguish these on the client side, curious to hear what that is.

And I hope clients are tolerant of the new 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
> Today, we will transmit both RMAppState.FINISHING and RMAppState.FINISHED to YarnApplicationState.FINISHED.

This message was sent by Atlassian JIRA

View raw message