Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1088344180.1216448431735.JavaMail.jira@brutus>
Date: Fri, 18 Jul 2008 23:20:31 -0700 (PDT)
From: "Billy Pearson (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-625) cluster load history: emissions and
 graphs
In-Reply-To: <990316702.1210696435622.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Billy Pearson commented on HBASE-625:
-------------------------------------

Now that we have a ttl option on the tables this would not be a bad idea as the users could modify the ttl to store the amount of history needed +1 on idea of a stats table idea.
also with it in a table all clients could query it from thrift, rest, or java api

> cluster load history: emissions and graphs
> ------------------------------------------
>
>                 Key: HBASE-625
>                 URL: https://issues.apache.org/jira/browse/HBASE-625
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>
> hbase should write loadings on a period in a format that is amenable to tools like ganglia (rrd).  Master can dump cluster loadings and averages.  Regionservers would report their own loadings.  Should exploit the work up in hadoop for doing this kinda thing (GangliaContext) where it makes sense.  Extra browning points if user can optionally enable display of graphs in the hbase UI (JRobin).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.