[
https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336451#comment-14336451
]
Tsuyoshi Ozawa commented on YARN-1809:
--------------------------------------
[~xgong] The failure of TestRMWebAppFairScheduler looks related - could you
double check?
Minor nits: ApplicationHistoryClientService.java: is cancelDelegationToken's
comment correct?
{code}
+ @Override
+ public CancelDelegationTokenResponse cancelDelegationToken(
+ CancelDelegationTokenRequest request) throws YarnException, IOException {
+ // TODO Auto-generated method stub
+ return null;
+ }
{code}
TestAHSWebServices.java: Noothing should be Nothing.
{code}
+ protected void serviceStart() throws Exception {
+ // Do Noothing
+ }
{code}
> 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.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)
