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-3230) Clarify application states on the web UI
Date Thu, 19 Feb 2015 23:11:12 GMT

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

Jason Lowe commented on YARN-3230:
----------------------------------

bq. NEW_SAVING: is not necessary to be seen by client?

I agree, it's not a state that seems relevant to a client.  We're not even consistent about
it, since FINAL_SAVING is not visible to clients and is silently translated to the previous
state.  However might be kind of hard to remove completely at this point since it's been published.

> Clarify application states on the web UI
> ----------------------------------------
>
>                 Key: YARN-3230
>                 URL: https://issues.apache.org/jira/browse/YARN-3230
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-3230.1.patch, YARN-3230.2.patch, YARN-3230.3.patch
>
>
> Today, application state are simply surfaced as a single word on the web UI. Not everyone
understands the meaning of "NEW_SAVING, SUBMITTED, ACCEPTED". This jira is to clarify the
meaning of these states, things like what the application is waiting for at this state. 
> In addition,the difference between application state and FinalStatus are fairly confusing
to users, especially when state=FINISHED, but FinalStatus=FAILED



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message