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

Ethan Wang updated PHOENIX-4370:
--------------------------------
    Description: 
Surface hbase metrics from perconnection to global metrics

Currently in phoenix client side, HBASE metrics are recorded and surfaced at 
Per Connection level. PHOENIX-4370 allow it to be aggregated at global level, 
i.e., aggregate across all connections within in one JVM so that user can 
evaluate it as a stable metrics periodically.

    COUNT_RPC_CALLS("rp", "Number of RPC calls"),
    COUNT_REMOTE_RPC_CALLS("rr", "Number of remote RPC calls"),
    COUNT_MILLS_BETWEEN_NEXTS("n", "Sum of milliseconds between sequential next 
calls"),
    COUNT_NOT_SERVING_REGION_EXCEPTION("nsr", "Number of 
NotServingRegionException caught"),
    COUNT_BYTES_REGION_SERVER_RESULTS("rs", "Number of bytes in Result objects 
from region servers"),
    COUNT_BYTES_IN_REMOTE_RESULTS("rrs", "Number of bytes in Result objects 
from remote region servers"),
    COUNT_SCANNED_REGIONS("rg", "Number of regions scanned"),
    COUNT_RPC_RETRIES("rpr", "Number of RPC retries"),
    COUNT_REMOTE_RPC_RETRIES("rrr", "Number of remote RPC retries"),
    COUNT_ROWS_SCANNED("ws", "Number of rows scanned"),
    COUNT_ROWS_FILTERED("wf", "Number of rows filtered");

  was:Surface hbase metrics from perconnection to global metrics


> Surface hbase metrics from perconnection to global metrics
> ----------------------------------------------------------
>
>                 Key: PHOENIX-4370
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4370
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Ethan Wang
>            Assignee: Ethan Wang
>
> Surface hbase metrics from perconnection to global metrics
> Currently in phoenix client side, HBASE metrics are recorded and surfaced at 
> Per Connection level. PHOENIX-4370 allow it to be aggregated at global level, 
> i.e., aggregate across all connections within in one JVM so that user can 
> evaluate it as a stable metrics periodically.
>     COUNT_RPC_CALLS("rp", "Number of RPC calls"),
>     COUNT_REMOTE_RPC_CALLS("rr", "Number of remote RPC calls"),
>     COUNT_MILLS_BETWEEN_NEXTS("n", "Sum of milliseconds between sequential 
> next calls"),
>     COUNT_NOT_SERVING_REGION_EXCEPTION("nsr", "Number of 
> NotServingRegionException caught"),
>     COUNT_BYTES_REGION_SERVER_RESULTS("rs", "Number of bytes in Result 
> objects from region servers"),
>     COUNT_BYTES_IN_REMOTE_RESULTS("rrs", "Number of bytes in Result objects 
> from remote region servers"),
>     COUNT_SCANNED_REGIONS("rg", "Number of regions scanned"),
>     COUNT_RPC_RETRIES("rpr", "Number of RPC retries"),
>     COUNT_REMOTE_RPC_RETRIES("rrr", "Number of remote RPC retries"),
>     COUNT_ROWS_SCANNED("ws", "Number of rows scanned"),
>     COUNT_ROWS_FILTERED("wf", "Number of rows filtered");



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to