[
https://issues.apache.org/jira/browse/HBASE-21301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658919#comment-16658919
]
Archana Katiyar commented on HBASE-21301:
-----------------------------------------
Thanks [~apurtell] and [~stack]. I will work on a user table with date-tiered
compaction policy enabled.
[~apurtell], Agreed on table_name_uid being 3 bytes and region_name_uid also 3
bytes. For region_uid, I followed similar pattern as openTSDB follows -
<metric_uid><timestamp><tagk1><tagv1>[...<tagkN><tagvN>]
region_uid is tag; other possible tags are store_file_uid, data_block_uid.
region_name_uid is value of region_uid tag.
We do have hierarchical relationship between regions --> store files --> data
blocks so explicitly adding tag uids can be avoid and row key can be -
<table_name_uid><timestamp
><metric_name_uid><region_name_uid><store_file_name_uid><data_block_name_uid>
But, I will prefer adding explicit tag uids because it helps in storing
non-hierarchical data too (if needed in future). Also, tag uids can be stored
in 1 byte; 2^8 unique tags should be good enough.
> 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
> Fix For: 3.0.0, 1.5.0, 2.2.0
>
>
> 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)
