Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
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.
Attachments
Attachments
Issue Links
- depends upon
-
YARN-1859 WebAppProxyServlet will throw ApplicationNotFoundException if the app is no longer cached in RM
-
- Closed
-
- incorporates
-
YARN-2048 List all of the containers of an application from the yarn web
-
- Resolved
-
- is blocked by
-
YARN-1819 ApplicationHistoryClientService#getApplications needs to be able to filter applications
-
- Open
-
-
YARN-1389 ApplicationClientProtocol and ApplicationHistoryProtocol should expose analogous APIs
-
- Closed
-
- is related to
-
YARN-1884 ContainerReport should have nodeHttpAddress
-
- Closed
-
-
YARN-1887 FairSchedulerAppsBlock and AppsBlock duplicate much code
-
- Open
-
-
YARN-1817 Synchronize RM and Generic History Service RESTful Web Services
-
- Open
-
- relates to
-
YARN-1462 AHS API and other AHS changes to handle tags for completed MR jobs
-
- Resolved
-
-
YARN-953 [YARN-321] Enable ResourceManager to write history data
-
- Closed
-
-
YARN-1685 Bugs around log URL
-
- Closed
-
-
YARN-1859 WebAppProxyServlet will throw ApplicationNotFoundException if the app is no longer cached in RM
-
- Closed
-