Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 13 Jul 2017 06:49:00 +0000 (UTC)
From: "Abhishek Singh Chouhan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13086822.1499928496000.236674.1499928540099@Atlassian.JIRA>
In-Reply-To: <JIRA.13086822.1499928496000@Atlassian.JIRA>
References: <JIRA.13086822.1499928496000@Atlassian.JIRA> <JIRA.13086822.1499928496426@jira-lw-us.apache.org>
Subject: [jira] [Created] (HBASE-18374) RegionServer Metrics improvements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 13 Jul 2017 06:49:06 -0000

Abhishek Singh Chouhan created HBASE-18374:
----------------------------------------------

             Summary: RegionServer Metrics improvements
                 Key: HBASE-18374
                 URL: https://issues.apache.org/jira/browse/HBASE-18374
             Project: HBase
          Issue Type: Improvement
    Affects Versions: 3.0.0
            Reporter: Abhishek Singh Chouhan
            Assignee: Abhishek Singh Chouhan
             Fix For: 3.0.0


At the RS level we have latency metrics for mutate/puts and deletes that are updated per batch (ie. at the end of entire batchop if it contains put/delete update the respective metric) in contrast with append/increment/get metrics that are updated per op. This is a bit ambiguous since the delete and put metrics are updated for multi row mutations that happen to contain a put/delete. We should rename the metric(eg. delete_batch)/add better description. Also we should add metrics for single delete client operations that come through RSRpcServer.mutate path. We should also add metrics for checkAndPut and checkAndDelete.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)