[
https://issues.apache.org/jira/browse/HBASE-21301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653412#comment-16653412
]
Archana Katiyar commented on HBASE-21301:
-----------------------------------------
I was looking at pros and cons of various options available in terms of
storage, retrieval and housekeeping (i.e. deleting older data); hbase table is
an obvious winner because here we have all the required functionality already
working at scale.
Since a new system table is a concern here; I was thinking of using a user
table for this. As per my understanding, the biggest difference (in this
context) between system table and user table is the chances of user table not
being available when we want to record stats.
When user accidentally dropped the required table, as a fallback we can store
in-memory stats for last 24 hours. We should also emit something to help
raising an alert that this table has been dropped. But we should be ensuring
that whenever the required table is re-created we should start using it again.
In-fact, when I think about the all corner possibilities here, it feels like
using a system table will be much more simpler.
[~andrew.purt...@gmail.com], [~stack] - I understand that there is overhead
with a new system table, but I feel this use-case and future similar use cases
are worthy enough to have a system table. Thoughts please?
> 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)
