[
https://issues.apache.org/jira/browse/HBASE-21301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649006#comment-16649006
]
stack commented on HBASE-21301:
-------------------------------
Thanks for working on this [~archana.katiyar]. Looks great.
High-level comments:
bq. Store data in a HBase table (new system table)
We have poor support for system tables currently. The hbase:namespace is a
system table that has caused us grief at assign time with a good while now. The
'fix' is to integrate it into the hbase:meta; i.e. have one system table only
that does all.
Keeping stats is a long-time request so excited to see progress. If they need
to persist, then they'll need a dedicated table. Does it have to be a 'system'
table? Does it have to be assigned before usertables? Or can stats recording go
on though the table is not deployed promptly? Or perhaps for v1, do as
[~allan163] suggests keeping in-memory circular buffers. Any visualization at
all even if just a report on the last few minutes of an in-memory buffer would
be a big massive win (smile).
Keeping stats, may I suggest taking a look at https://datasketches.github.io/
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)
