phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Shrivastava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3655) Metrics for PQS
Date Tue, 22 Aug 2017 23:14:01 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137581#comment-16137581
] 

Rahul Shrivastava commented on PHOENIX-3655:
--------------------------------------------

[~elserj] [~jamestaylor] [~samarthjain]

Hi All,

I guess we may start the discussion on how we want the metrics collection to be designed for
Phoenix Query Server. 

I would lay down options and you can provide your input to them ( or even add another option)

1. Write a layer to convert from the Phoenix internal representation to the metrics system
of choice (a shim). -- as suggested by [~elserj]
2. write the request level metrics at event close ( statement close, connection close ) and
push the data down to Phoenix tables itself. We would create bootstrap tables in Phoenix and
write down every request/global level metrics.  That way, we will have options to collect
the metrics later by querying the tables. We can have Phoenix level parameter which will limit
the length of time metrics could be retained. 

Please advise.

thanks
Rahul


> 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
>            Assignee: Rahul Shrivastava
>             Fix For: 4.12.0
>
>         Attachments: MetricsforPhoenixQueryServerPQS.pdf
>
>   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.4.14#64029)

Mime
View raw message