[
https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-1809:
------------------------------
Attachment: YARN-1809.8.patch
I upload a patch, which fixed some bugs I've found on the web pages.
In addition, I've tested the new RM web UI on the secured cluster, via https.
It was working fine as well.
One issue I've found is that node in the old RM web UI is a link to the NM web
page, however, the new RM web UI and AHS web UI uniformly get container report
from ApplicationBaseProtocol and fill the web page with the report. The
container report doesn't contain nodeHttpAddress yet. I filed a separate ticket
to track this issue (YARN-1884). Temporally, I disable the link and just show
the node ID where the container was running.
> 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: Bug
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Attachments: YARN-1809.1.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
>
>
> 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.2#6252)
