Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 15 Nov 2012 19:45:15 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1386884756.120697.1353008715178.JavaMail.jiratomcat@arcas>
In-Reply-To: <699590106.109317.1352833574073.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-7157) Report Metrics into an HBase table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Enis Soztutar commented on HBASE-7157:
--------------------------------------

bq. What you referring to when you say this
I remember from some jira discussion about introducing special system tables, as Anoop describes above. Like the catalog tables, they are managed, and deployed from hbase internals (like the SQL INFORMATION_SCHEMA). Our ACL table is already a system table in this respect. 
                
> Report Metrics into an HBase table
> ----------------------------------
>
>                 Key: HBASE-7157
>                 URL: https://issues.apache.org/jira/browse/HBASE-7157
>             Project: HBase
>          Issue Type: Improvement
>          Components: metrics
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>
> Right now metrics are sent using ServerLoad and RegionLoad to the master.  We should store those(and other) metrics in a table.  Storing these metrics in a table will allow the LoadBalancer to have more context.  In addition those metrics will be useful for the ui.

--
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