You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/08/18 04:30:18 UTC
[jira] [Updated] (PHOENIX-195) Gather and maintain stats for HBase
tables in a designated HBase table
[ https://issues.apache.org/jira/browse/PHOENIX-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-195:
---------------------------------
Issue Type: Sub-task (was: Task)
Parent: PHOENIX-1177
> Gather and maintain stats for HBase tables in a designated HBase table
> ----------------------------------------------------------------------
>
> Key: PHOENIX-195
> URL: https://issues.apache.org/jira/browse/PHOENIX-195
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: ramkrishna.s.vasudevan
>
> Our current stats gathering is way too simplistic - it's only keeping a cache per client connection to a cluster for the min and max key for a table. Instead, we should:
> 1. have a system table that stores the stats
> 2. create a coprocessor that updates the stats during compaction (i.e. using the preCompactSelection, postCompactSelection, preCompact, postCompact methods)
> 3. keep a kind of histogram - the key boundary of every N bytes within a region. Perhaps we can do a delta update on minor compaction and a complete update on major compaction.
> 4. keep the min key/max key of a table in the stats table too
--
This message was sent by Atlassian JIRA
(v6.2#6252)