[
https://issues.apache.org/jira/browse/YARN-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-954:
-----------------------------
Attachment: YARN-954.4.patch
I reworked on the webUI:
1. I forked the AppsBlock, AppBlock from RM, and added AppAttemptBlock and
ContainerBlock, which are place in yarn-server-common. After some
investigation, I though it would be too much work to uniform RM/NM/AHS web
page. What I did is to promote ApplicationHistoryManger to ApplicationContext,
which returns the reports of App/Attempt/Container, and all the web pages
should use it get the data source. For example, ApplicationHistoryManger
implements it to get the data source from the history store. In the future, we
should have an RM implementation to wrap RMContext. A side benefit or working
based on the reports is to uniform the results via RPC interface and
webUI/services.
2. I simplified the web pages we need, and made it as much similar as possible
to the RM webUI. Not the structure is:
Applications
--------------- Application (with the list of attempts)
----------------------------- Application Attempt (with the list of containers)
------------------------------------------------------ Container
3. Like RM webUI, I created XXXXInfo, and wrap the report into the XXXXInfo,
before bringing it to html content.
> [YARN-321] History Service should create the webUI and wire it to
> HistoryStorage
> --------------------------------------------------------------------------------
>
> Key: YARN-954
> URL: https://issues.apache.org/jira/browse/YARN-954
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Zhijie Shen
> Attachments: YARN-954-3.patch, YARN-954-v0.patch, YARN-954-v1.patch,
> YARN-954-v2.patch, YARN-954.4.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
