Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Tue, 22 Mar 2016 18:49:25 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12952546.1458672513000.20761.1458672565556@Atlassian.JIRA>
In-Reply-To: <JIRA.12952546.1458672513000@Atlassian.JIRA>
References: <JIRA.12952546.1458672513000@Atlassian.JIRA>
 <JIRA.12952546.1458672513236@arcas>
Subject: [jira] [Created] (HBASE-15518) Add Per-Table metrics back
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Enis Soztutar created HBASE-15518:
-------------------------------------

             Summary: Add Per-Table metrics back
                 Key: HBASE-15518
                 URL: https://issues.apache.org/jira/browse/HBASE-15518
             Project: HBase
          Issue Type: Sub-task
            Reporter: Enis Soztutar
            Assignee: Alicia Ying Shu
             Fix For: 2.0.0, 1.4.0


We used to have per-table metrics, but it was removed in some restructuring. We have per-region metrics, and per-regionserver metrics, but nothing in between. 

For majority of users, per-region is too granular, they are mostly interested in table level aggregates. This is especially useful in multi-tenant cases where a table's disk usage, number of requests, etc can be made much more visible. 

In this jira, we'll add the basic infrastructure to add a single (or a few) per-table metrics. Than we can improve on that by adding remaining metrics from the region server level. 

The plan is to NOT aggregate per-table metrics at master for now. Just aggregation of per-region metrics at the per-table level for every regionserver. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)