phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes
Date Thu, 13 Jul 2017 22:17:00 GMT

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

Josh Elser commented on PHOENIX-3807:
-------------------------------------

bq. Here's a patch which uses the HBase native metrics API. There's a check for HBase version
>= 1.4 for backwards compatibility, and a config flag.

Um, I'm starting to understand why this wasn't in patch-available :)

The new metrics API only shows up in HBase 1.4 (of which there is no such release yet)

> Add server level metrics for secondary indexes
> ----------------------------------------------
>
>                 Key: PHOENIX-3807
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3807
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Vincent Poon
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-3807.v1.master.patch, PHOENIX-3807.v2.patch, PHOENIX-3807.v3.patch,
Screen Shot 2017-05-31 at 4.00.16 PM.png
>
>
> Add server level metrics for secondary indexes
> - Histogram metrics for time to complete all secondary index updates per primary table
update per index type. Will help us trend perf over time and catch impending issues. 
> - Histogram metrics for number of updates dispatched to secondary index stores to service
one primary table update per index type. Will help us catch inefficient behavior or problematic
schema design. 
> - Count of deployed secondary indexes by type. Will help understand and trend index usage,
or catch deploy of an unwanted index type.



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

Mime
View raw message