hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not
Date Thu, 01 Aug 2013 04:29:55 GMT

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

Zhijie Shen commented on YARN-808:

+1 for embedding ApplicationAttemptReport in ApplicationReport.

Think it out loudly. I've a concern that with more info to be fetched, getApplicationReport
is likely to be slower, and the response message is likely to be bigger. However, users may
not always want to know all the info of an application, such as the embedded ApplicationAttemptReport,
right? Sometimes users just want to fetch partial information of an application to speed up
the response. Thoughts?
> ApplicationReport does not clearly tell that the attempt is running or not
> --------------------------------------------------------------------------
>                 Key: YARN-808
>                 URL: https://issues.apache.org/jira/browse/YARN-808
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta
>            Reporter: Bikas Saha
>            Assignee: Xuan Gong
>         Attachments: YARN-808.1.patch
> When an app attempt fails and is being retried, ApplicationReport immediately gives the
new attemptId and non-null values of host etc. There is no way for clients to know that the
attempt is running other than connecting to it and timing out on invalid host. Solution would
be to expose the attempt state or return a null value for host instead of "N/A"

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message