[jira] [Commented] (HBASE-7057) Store Server Load in a Table

["stack (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-7057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485075#comment-13485075 ] 

stack commented on HBASE-7057:
------------------------------

Chatting w/ Elliott more on this:

+ sequence id should probably be in .META.
+ having some metrics history would be sweet.  We could let it TTL out after an hour so we didn't keep too much around (or after an hour do the TSDB rollups if wanted)
+ A TSDB like query page for looking at the cluster over time would be sweet.
+ We should be careful to ensure we do not repeat the mistakes of the distant past when we used to keep a region history table into which we noted region transition; the problem there was our trying to record events like close when say, the cluster was going down, and the table we were trying to write would be down -- the writer could hang

This seems like a small thing to do that could improve usability alot.
                
> Store Server Load in a Table
> ----------------------------
>
>                 Key: HBASE-7057
>                 URL: https://issues.apache.org/jira/browse/HBASE-7057
>             Project: HBase
>          Issue Type: Improvement
>          Components: metrics, UI
>    Affects Versions: 0.96.0
>            Reporter: Elliott Clark
>              Labels: noob
>             Fix For: 0.98.0
>
>
> Currently the server hart beat sends over server load and region loads.  This is used to display and store metrics about a region server.  It is also used to remember the sequence id of flushes.
> This should be moved into an HBase table.  
> * Allow the last sequence id to persist over a master restart.
> * That would allow the balancer to have a more complete picture of what's happened in the past.
> * Allow tools to be created to monitor hbase using hbase.
> * Simplify/remove the heartbeat.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira