[
https://issues.apache.org/jira/browse/HIVE-10761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574181#comment-14574181
]
Gopal V commented on HIVE-10761:
--------------------------------
Setting {{hive.server2.metrics.enabled=true}} seems to trigger another error
{code}
2015-06-05 02:18:28,818 ERROR [main()]: server.HiveServer2
(HiveServer2.java:stop(314)) - error in Metrics deinit:
java.lang.NullPointerException null
java.lang.NullPointerException
at org.apache.hive.service.server.HiveServer2.stop(HiveServer2.java:312)
at
org.apache.hive.service.server.HiveServer2.startHiveServer2(HiveServer2.java:387)
at
org.apache.hive.service.server.HiveServer2.access$700(HiveServer2.java:75)
at
org.apache.hive.service.server.HiveServer2$StartOptionExecutor.execute(HiveServer2.java:609)
at org.apache.hive.service.server.HiveServer2.main(HiveServer2.java:482)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
{code}
> Create codahale-based metrics system for Hive
> ---------------------------------------------
>
> Key: HIVE-10761
> URL: https://issues.apache.org/jira/browse/HIVE-10761
> Project: Hive
> Issue Type: New Feature
> Components: Diagnosability
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Fix For: 1.3.0
>
> Attachments: HIVE-10761.2.patch, HIVE-10761.3.patch,
> HIVE-10761.4.patch, HIVE-10761.5.patch, HIVE-10761.6.patch, HIVE-10761.patch,
> hms-metrics.json
>
>
> There is a current Hive metrics system that hooks up to a JMX reporting, but
> all its measurements, models are custom.
> This is to make another metrics system that will be based on Codahale (ie
> yammer, dropwizard), which has the following advantage:
> * Well-defined metric model for frequently-needed metrics (ie JVM metrics)
> * Well-defined measurements for all metrics (ie max, mean, stddev, mean_rate,
> etc),
> * Built-in reporting frameworks like JMX, Console, Log, JSON webserver
> It is used for many projects, including several Apache projects like Oozie.
> Overall, monitoring tools should find it easier to understand these common
> metric, measurement, reporting models.
> The existing metric subsystem will be kept and can be enabled if backward
> compatibility is desired.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
