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 2018/03/16 00:58:00 UTC

[jira] [Commented] (HIVE-18971) add HS2 WM metrics for use in Grafana and such

    [ https://issues.apache.org/jira/browse/HIVE-18971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401332#comment-16401332 ] 

Sergey Shelukhin commented on HIVE-18971:
-----------------------------------------

For now the metrics will only reflect HS2 side info and it looks like they will use Hadoop metrics directly for metrics per pool, and only output totals to Codahale, because codahale has no capacity for tagging the way it's set up as a singleton, with a single process wide context and no sessionId or such things. 
We may later rework how codahale works in Hive to support those (in a separate JIRA).
Getting runtime information from AM side (e.g. how many guaranteed tasks are used per pool) would require either changing tagging to be pool based instead of dag based (and removing session ID, meaningless in this context, to be replaced with dag ID, I guess), or propagating it via progress (which is probably better, but requires changes to Tez).

> add HS2 WM metrics for use in Grafana and such
> ----------------------------------------------
>
>                 Key: HIVE-18971
>                 URL: https://issues.apache.org/jira/browse/HIVE-18971
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>            Priority: Major
>
> HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 even sets up metrics right now...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)