hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3603) Application Attempts page confusing
Date Fri, 18 Sep 2015 11:46:04 GMT

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

Sunil G commented on YARN-3603:

Hi [~jeffzhang]
Thank you for pointing this. {{Container Exit Status}} must not be present in AppAttempt page.
I will remove the same and upload a patch.

For RM WebUI, we are using {{ClientRMService}} alone, and ATS/AHS is not contacted here to
get container info. Also RM keeps tracks of running containers here and the idea is to keep
information about completed containers in ATS/AHS UI. When application is finished/running,
ATS UI is capable of giving detailed information about the application (containers info also).

> Application Attempts page confusing
> -----------------------------------
>                 Key: YARN-3603
>                 URL: https://issues.apache.org/jira/browse/YARN-3603
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: webapp
>    Affects Versions: 2.8.0
>            Reporter: Thomas Graves
>            Assignee: Sunil G
>         Attachments: 0001-YARN-3603.patch, 0002-YARN-3603.patch, 0003-YARN-3603.patch,
> The application attempts page (http://RM:8088/cluster/appattempt/appattempt_1431101480046_0003_000001)
> is a bit confusing on what is going on.  I think the table of containers there is for
only Running containers and when the app is completed or killed its empty.  The table should
have a label on it stating so.  
> Also the "AM Container" field is a link when running but not when its killed.  That might
be confusing.
> There is no link to the logs in this page but there is in the app attempt table when
looking at http://
> rm:8088/cluster/app/application_1431101480046_0003

This message was sent by Atlassian JIRA

View raw message