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

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1, 1.3.0, 1.4.0, 1.5.0, 2.0.0, 2.1.5, 2.2.1
• Fix Version/s: 3.0.0-alpha-1, 2.3.0, 1.6.0, 2.1.8, 2.2.3
• Component/s: canary
• Hadoop Flags: Reviewed

Release Note

Added a comment to make clear that read/write success counts are tallying column family success counts, not region success counts.

Additionally, the region read and write latencies previously only stored the latencies of the last column family of the region reads/writes. This has been fixed by using a map of each region to a list of read and write latency values.

• Assignee: Caroline Zhou
• Reporter: Caroline Zhou
• Created: 14/Oct/19 23:31
• Updated: 22/Oct/19 15:17
• Resolved: 21/Oct/19 16:21

Description

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.