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

Archana Katiyar commented on HBASE-21301:
-----------------------------------------

[~apurtell] I was working on the schema to store access stats, based on openTSB 
schema. openTSB is very good in terms of minimizing the row key size by using 
binary encoding. _But one overhead I see is to have a separate table to store 
UID mappings_. For our use-case, we need to store UID corresponding to table 
name, metric name (like read count\ write count) and region name etc.

We can have row key like -

<table_name_uid - 1 byte><timestamp - 4 bytes><metric_name_uid - 1 
byte><region_uid - 1 byte><region_name_uid - x bytes>

I have started the key with table name instead of timestamp to better 
distribute the load.

In future, when we enable the stats for store file, we can append store file 
name uid also to the row key.

> Heatmap for key access patterns
> -------------------------------
>
>                 Key: HBASE-21301
>                 URL: https://issues.apache.org/jira/browse/HBASE-21301
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Archana Katiyar
>            Assignee: Archana Katiyar
>            Priority: Major
>
> Google recently released a beta feature for Cloud Bigtable which presents a 
> heat map of the keyspace. *Given how hotspotting comes up now and again here, 
> this is a good idea for giving HBase ops a tool to be proactive about it.* 
> >>>
> Additionally, we are announcing the beta version of Key Visualizer, a 
> visualization tool for Cloud Bigtable key access patterns. Key Visualizer 
> helps debug performance issues due to unbalanced access patterns across the 
> key space, or single rows that are too large or receiving too much read or 
> write activity. With Key Visualizer, you get a heat map visualization of 
> access patterns over time, along with the ability to zoom into specific key 
> or time ranges, or select a specific row to find the full row key ID that's 
> responsible for a hotspot. Key Visualizer is automatically enabled for Cloud 
> Bigtable clusters with sufficient data or activity, and does not affect Cloud 
> Bigtable cluster performance. 
> <<<
> From 
> [https://cloudplatform.googleblog.com/2018/07/on-gcp-your-database-your-way.html]
> (Copied this description from the write-up by [~apurtell], thanks Andrew.)



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

Reply via email to