[
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.9.patch
Talked to Vinod offline about the patch and made following changes in the new
one:
1. Mark ApplicationBaseProtocol \@Private
2. Mark ApplicationHistoryManager \@Private
3. Revert the hack code for FairSchedulerAppsBlock, and I just simply duplicate
most code of AppsBlock, as the old FairSchedulerAppsBlock duplicates the old
AppsBlock. I'll file a separate Jira to tackle the refactoring of
FairSchedulerAppsBlock.
> 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: 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, 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.2#6252)
