You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2015/08/24 19:57:46 UTC
[jira] [Comment Edited] (HIVE-11526) LLAP: implement LLAP UI as a
separate service
[ https://issues.apache.org/jira/browse/HIVE-11526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709726#comment-14709726 ]
Sergey Shelukhin edited comment on HIVE-11526 at 8/24/15 5:56 PM:
------------------------------------------------------------------
I think the app name is the argument to the "$for" method. So, the monitor can use a different name, in the same or different class.
The standard jmx, stack and conf pages do not require any resources in that directory
was (Author: sershe):
I think the app name is the argument to the "$for" method. So, the monitor can use a different name.
The standard jmx, stack and conf pages do not require any resources in that directory
> LLAP: implement LLAP UI as a separate service
> ---------------------------------------------
>
> Key: HIVE-11526
> URL: https://issues.apache.org/jira/browse/HIVE-11526
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sergey Shelukhin
> Assignee: Kai Sasaki
> Attachments: llap_monitor_design.pdf
>
>
> The specifics are vague at this point.
> Hadoop metrics can be output, as well as metrics we collect and output in jmx, as well as those we collect per fragment and log right now.
> This service can do LLAP-specific views, and per-query aggregation.
> [~gopalv] may have some information on how to reuse existing solutions for part of the work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)