hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs
Date Thu, 05 Mar 2015 01:55:39 GMT

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

Jian He commented on YARN-1809:
-------------------------------

looks good overall.
- the app page seems corrupted. 
- ContainerExitStatus for running containers better to be “N/A”
- the “node” link seems wrong, it looks to be the rpc port instead of http port;
- revert import changes only in AppsBlockWithMetrics, CapacitySchedulerPage, DefaultSchedulerPage

> Synchronize RM and Generic History Service Web-UIs
> --------------------------------------------------
>
>                 Key: YARN-1809
>                 URL: https://issues.apache.org/jira/browse/YARN-1809
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Zhijie Shen
>            Assignee: Xuan Gong
>         Attachments: YARN-1809.1.patch, YARN-1809.10.patch, YARN-1809.11.patch, YARN-1809.12.patch,
YARN-1809.13.patch, YARN-1809.14.patch, YARN-1809.15-rebase.patch, YARN-1809.15.patch, YARN-1809.16.patch,
YARN-1809.2.patch, YARN-1809.3.patch, YARN-1809.4.patch, YARN-1809.5.patch, YARN-1809.5.patch,
YARN-1809.6.patch, YARN-1809.7.patch, YARN-1809.8.patch, YARN-1809.9.patch
>
>
> After YARN-953, the web-UI of generic history service is provide more information than
that of RM, the details about app attempt and container. It's good to provide similar web-UIs,
but retrieve the data from separate source, i.e., RM cache and history store respectively.



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

Mime
View raw message