phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karan Mehta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4736) PQS statement and connection metrics handling
Date Thu, 10 May 2018 22:28:00 GMT

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

Karan Mehta updated PHOENIX-4736:
---------------------------------
    Summary: PQS statement and connection metrics handling  (was: PQS Client side Metrics
Handling )

> PQS statement and connection metrics handling
> ---------------------------------------------
>
>                 Key: PHOENIX-4736
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4736
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Karan Mehta
>            Priority: Major
>
> Phoenix fat client exposes a number of metrics at StatementLevel as well as ConnectionLevel.
PQS uses avatica server and exposes two metrics at this point of time, which is request end
to end time and request serialization/deserialization time. These metrics are not super useful
for PQS operations POV, however we need them to track the bad client and mis-usage.
> This Jira is to discuss how we should handle those metrics. 
> 1. As pointed by [~jamestaylor], we can use SYSTEM.LOG table as a potential option here. 
> 2. Write a shim layer to convert the metrics to hbase-metrics, which internally uses
hadoop-metrics2 and define fine sink as the output.
> Additional ideas welcome.
> [~elserj] [~apurtell] [~tdsilva] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message