[
https://issues.apache.org/jira/browse/HIVE-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922412#comment-16922412
]
Laszlo Bodor commented on HIVE-22149:
-------------------------------------
e.g. Cloudera Manager relies on codahale metrics, and I faced a situation where
I had to decide whether I'll change CM code in order to integrate to metastore
service properly or unify these keys with the corresponding keys in hiveserver2
metric file (I did the latter)
unfortunately, as standalone-metastore should be able to be built independently
from other parts of hive, I cannot refactor this logic to a common place
> Metastore: Unify codahale metrics.log json structure between hiveserver2 and
> metastore services
> -----------------------------------------------------------------------------------------------
>
> Key: HIVE-22149
> URL: https://issues.apache.org/jira/browse/HIVE-22149
> Project: Hive
> Issue Type: Bug
> Reporter: Laszlo Bodor
> Assignee: Laszlo Bodor
> Priority: Major
> Attachments: HIVE-22149.01.patch, metrics_hiveserver2.log,
> metrics_metastore.log
>
>
> While fixing HIVE-22140 I found some really annoying differences between the
> codahale metric file structures between hiveserver2 and metastore, e.g.
> open_connections: can be found in "counters" for hs2, but in "gauges" for ms
> threads count: it's a proper "threads.count" for hs2, but a really ambiguous
> "count" for ms
> so I realized that "memory." and "threads." prefix is completely absent in ms
> metrics file, which is misleading
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
