You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Xuan Gong (JIRA)" <ji...@apache.org> on 2015/07/22 00:26:04 UTC
[jira] [Commented] (YARN-3299) Synchronize RM and Generic History
Service Web-UIs
[ https://issues.apache.org/jira/browse/YARN-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635940#comment-14635940 ]
Xuan Gong commented on YARN-3299:
---------------------------------
Resolving this umbrella JIRA. And as new requirements/bugs come in, we can open new tickets.
* Will leave the open sub-tasks as they are.
* No fix-version as this was done across releases.
> Synchronize RM and Generic History Service Web-UIs
> --------------------------------------------------
>
> Key: YARN-3299
> URL: https://issues.apache.org/jira/browse/YARN-3299
> Project: Hadoop YARN
> Issue Type: Task
> Components: resourcemanager, webapp, yarn
> Reporter: Xuan Gong
> Assignee: Xuan Gong
>
> After YARN-1809, we are using the same protocol to fetch the information and display in their webUI. RM webUI will use ApplicationClientProtocol, and Generic History Service web ui will use ApplicationHistoryProtocol. Both of them extend the same protocol.
> Also, we have common appblock/attemptblock/containerblock shared by both RM webUI and ATS webUI.
> But we are still missing some information, such as outstanding resource requests, preemption metrics, etc.
> This ticket will be used as parent ticket to track all the remaining issues for RM webUI and ATS webUI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)