You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Yu Li (JIRA)" <ji...@apache.org> on 2016/02/06 17:39:39 UTC

[jira] [Commented] (HBASE-15160) Put back HFile's HDFS op latency sampling code and add metrics for monitoring

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

Yu Li commented on HBASE-15160:
-------------------------------

Just noticed this comment... Could you point me to the JIRA number sir? Thanks.

We didn't observe the perf downgrade in our applications, but maybe neglected somehow. To be cautious, I'll perform some comparison testing on the scan with multiple CF scenario and get back with the number later.

> 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, HBASE-15160_v2.patch, HBASE-15160_v3.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)