Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1198119B32 for ; Thu, 7 Apr 2016 18:03:26 +0000 (UTC) Received: (qmail 24914 invoked by uid 500); 7 Apr 2016 18:03:25 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 24875 invoked by uid 500); 7 Apr 2016 18:03:25 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 24856 invoked by uid 99); 7 Apr 2016 18:03:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Apr 2016 18:03:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 95A3C2C1F69 for ; Thu, 7 Apr 2016 18:03:25 +0000 (UTC) Date: Thu, 7 Apr 2016 18:03:25 +0000 (UTC) From: "Alicia Ying Shu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-15518) Add Per-Table metrics back MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-15518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230723#comment-15230723 ] Alicia Ying Shu commented on HBASE-15518: ----------------------------------------- The test hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures passed on my local box. > 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 > > Attachments: HBASE-15518-v1.patch, HBASE-15518.patch > > > 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)