Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 11 Feb 2013 19:25:13 +0000 (UTC)
From: "Tianying Chang (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12631793.1360610626280.274314.1360610713095@arcas>
In-Reply-To: <JIRA.12631793.1360610626280@arcas>
References: <JIRA.12631793.1360610626280@arcas>
Subject: [jira] [Created] (HBASE-7818) add region level metrics
 readReqeustCount and writeRequestCount
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Tianying Chang created HBASE-7818:
-------------------------------------

             Summary: add region level metrics readReqeustCount and writeRequestCount 
                 Key: HBASE-7818
                 URL: https://issues.apache.org/jira/browse/HBASE-7818
             Project: HBase
          Issue Type: Improvement
          Components: metrics
    Affects Versions: 0.94.4
            Reporter: Tianying Chang
            Assignee: Tianying Chang
            Priority: Minor
             Fix For: 0.94.6


Request rate at region server level can help identify the hot region server. But it will be good if we can further identify the hot regions on that region server. That way, we can easily find out unbalanced regions problem. 

Currently, readRequestCount and writeReqeustCount per region is exposed at webUI. It will be more useful to expose it through hadoop metrics framework and/or JMX, so that people can see the history when the region is hot.

I am exposing the existing readRequestCount/writeRequestCount into the dynamic region level metrics framework. I am not changing/exposing it as rate because our openTSDB is taking the raw data of read/write count, and apply rate function to display the rate already. 


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