phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-3067) Phoenix metrics system should not be started in mini-cluster mode
Date Tue, 08 Jan 2019 23:01:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas D'Silva updated PHOENIX-3067:
------------------------------------
    Fix Version/s:     (was: 4.15.0)

> Phoenix metrics system should not be started in mini-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
>            Priority: Major
>         Attachments: phoenix-3067_v1.patch
>
>
> 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
(v7.6.3#76005)

Mime
View raw message