Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 25 Jan 2016 20:50:39 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12933733.1453701814000.204542.1453755039974@Atlassian.JIRA>
In-Reply-To: <JIRA.12933733.1453701814000@Atlassian.JIRA>
References: <JIRA.12933733.1453701814000@Atlassian.JIRA>
 <JIRA.12933733.1453701814227@arcas>
Subject: [jira] [Commented] (HBASE-15160) Put back HFile's HDFS op latency
 sampling code and add metrics for monitoring
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Elliott Clark commented on HBASE-15160:
---------------------------------------

Rather than storing the times, we should just put them into a histogram in the metrics system.

Something like compaction time does.

> Put back HFile's HDFS op latency sampling code and add metrics for monitoring
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-15160
>                 URL: https://issues.apache.org/jira/browse/HBASE-15160
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0, 1.1.2
>            Reporter: Yu Li
>            Assignee: Yu Li
>         Attachments: HBASE-15160.patch
>
>
> In HBASE-11586 all HDFS op latency sampling code, including fsReadLatency, fsPreadLatency and fsWriteLatency, have been removed. There was some discussion about putting them back in a new JIRA but never happened. According to our experience, these metrics are useful to judge whether issue lies on HDFS when slow request occurs, so we propose to put them back in this JIRA, and add the metrics for monitoring as well.


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