[
https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864668#comment-15864668
]
Josh Elser commented on PHOENIX-3655:
-------------------------------------
bq. we want the PQS driver to export the same metrics through the same
mechanism(s) as the fat driver. That way we can swap one for the other with
minimal operational changes including visibility into operations via metrics.
Makes sense. I've spent a lot (too much?) time thinking about this from the
Avatica standpoint (understanding the perf/characteristics of Avatica,
regardless of database), so I may be conflating what [~rahulshrivastava] is
planning with the big picture of what I'd like to see :)
If the goal is to just expose the thick-driver's metrics via PQS, this one
should be pretty easy. If we want to go farther and really understand the rest
of the picture, it gets trickier pretty fast :)
> Metrics for PQS
> ---------------
>
> Key: PHOENIX-3655
> URL: https://issues.apache.org/jira/browse/PHOENIX-3655
> Project: Phoenix
> Issue Type: New Feature
> Affects Versions: 4.8.0
> Environment: Linux 3.13.0-107-generic kernel, v4.9.0-HBase-0.98
> Reporter: Rahul Shrivastava
> Fix For: 4.9.0
>
> Original Estimate: 240h
> Remaining Estimate: 240h
>
> Phoenix Query Server runs a separate process compared to its thin client.
> Metrics collection is currently done by PhoenixRuntime.java i.e. at Phoenix
> driver level. We need the following
> 1. For every jdbc statement/prepared statement/ run by PQS , we need
> capability to collect metrics at PQS level and push the data to external sink
> i.e. file, JMX , other external custom sources.
> 2. Besides this global metrics could be periodically collected and pushed to
> the sink.
> 2. PQS can be configured to turn on metrics collection and type of collect (
> runtime or global) via hbase-site.xml
> 3. Sink could be configured via an interface in hbase-site.xml.
> All metrics definition https://phoenix.apache.org/metrics.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
