You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2019/10/18 05:05:00 UTC

[jira] [Commented] (HBASE-23172) HBase Canary region success count metrics reflect column family successes, not region successes

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

Michael Stack commented on HBASE-23172:
---------------------------------------

+1



> HBase Canary region success count metrics reflect column family successes, not region successes
> -----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-23172
>                 URL: https://issues.apache.org/jira/browse/HBASE-23172
>             Project: HBase
>          Issue Type: Improvement
>          Components: canary
>    Affects Versions: 3.0.0, 1.3.0, 1.4.0, 1.5.0, 2.0.0, 2.1.5, 2.2.1
>            Reporter: Caroline
>            Assignee: Caroline
>            Priority: Minor
>         Attachments: HBASE-23172.branch-1.000.patch, HBASE-23172.branch-2.000.patch, HBASE-23172.master.000.patch
>
>
> HBase Canary reads once per column family per region. The current "region success count" should actually be "column family success count," which means we need another metric that actually reflects region success count. Additionally, the region read and write latencies only store the latencies of the last column family of the region read. Instead of a map of regions to a single latency value and success value, we should map each region to a list of such values.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)