Enis Soztutar created PHOENIX-3067:
--------------------------------------
Summary: Phoenix metrics system should not be started in
pseudo-cluster mode
Key: PHOENIX-3067
URL: https://issues.apache.org/jira/browse/PHOENIX-3067
Project: Phoenix
Issue Type: Bug
Reporter: Enis Soztutar
Assignee: Enis Soztutar
Fix For: 4.9.0
Phoenix tracing piggy-backs on the metrics system by specifying a SpanReceiver
which is also a MetricsSource (TraceMetricsSource).
This works differently on client side versus server side. The hadoop metrics
system should only be initialized once, and can only have a single prefix
(hbase or phoenix, etc). We configure the metric sink through
hadoop-metrics2.properties differently in client side versus server side [1].
Hadoop metric system is designed so that if it is initialized already with some
prefix (like hbase), re-initializing it again will be ignored unless it is in
"mini-cluster mode". We do not check whether the metrics is already initialized
from {{Metrics.java}} and blindly call
{{DefaultMetricsSystem.instance().init("phoenix")}} which works as long as we
are in distributed mode. Otherwise, the metrics sinks do not work.
[1] https://phoenix.apache.org/tracing.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
