You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2016/04/05 11:55:25 UTC
[jira] [Created] (AMBARI-15708) "Wrong metrics path " exceptions
for JMX metrics
Dmytro Sen created AMBARI-15708:
-----------------------------------
Summary: "Wrong metrics path " exceptions for JMX metrics
Key: AMBARI-15708
URL: https://issues.apache.org/jira/browse/AMBARI-15708
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 2.2.2
{code}
04 Apr 2016 17:54:27,561 ERROR [pool-10-thread-2264] BaseProvider:240 - Caught exception getting JMX metrics : Can not fetch 0th element of document path (executorsTotal._sum) from json. Wrong metrics path: /api/v1/cluster/summary##executorsTotal._sum, skipping same exceptions for next 5 minutes
java.io.IOException: Can not fetch 0th element of document path (executorsTotal._sum) from json. Wrong metrics path: /api/v1/cluster/summary##executorsTotal._sum
at org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:445)
at org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.populateResource(RestMetricsPropertyProvider.java:234)
at org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:180)
at org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$1.call(ThreadPoolEnabledPropertyProvider.java:178)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{code}
AmbariMetaInfo adds aggregated functions for jmx metrics, but should add only for ams metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)