[ https://issues.apache.org/jira/browse/HBASE-21301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653835#comment-16653835 ]
stack commented on HBASE-21301: ------------------------------- All of the above sounds great [~archana.katiyar]. Yes, a table makes best sense. Could be a table that used the date-tiered compaction so older-than-30-days gets left alone; later, can work on a mechanism to just drop the aged hfiles rather have compaction rewrite the data dropping old version. It can be a 'system' table but not depend on being assigned ahead of use-tables. If the table is not present, there will be lots of complaint in logs. Easy for operator to fix by creating table. I'd suggest no need of an auto-create in each RegionServer -- punt to operator. Perhaps supply a script to create the table on setup? Thanks. > 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)