Vinod Kumar Vavilapalli updated YARN-1809:
    Fix Version/s: 2.6.1

Pulled this into 2.6.1. Ran compilation and 
TestApplicationHistoryClientService, TestAHSWebApp, TestAHSWebServices, 
TestAppPage, TestRMWebApp, TestRMWebAppFairScheduler before the push. Patch did 
not apply cleanly, had to manage some merge conflicts and code reorg.

> 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: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Xuan Gong
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.0, 2.6.1
>         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.17.patch, YARN-1809.17.rebase.patch, 
> YARN-1809.17.rebase.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

Reply via email to