You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Javier Akira Luca de Tena (Jira)" <ji...@apache.org> on 2020/09/08 03:28:00 UTC

[jira] [Updated] (HBASE-24994) Add hedgedReadOpsInCurThread metric

     [ https://issues.apache.org/jira/browse/HBASE-24994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Javier Akira Luca de Tena updated HBASE-24994:
----------------------------------------------
    Description: 
When adding Hedged Reads metrics at https://issues.apache.org/jira/browse/HBASE-12220, hedgedReadOpsInCurThread was not included.

I wonder if there was any reason to not include them. If not, I will provide pull request to include them soon.

This metric is very useful the determine if the hedged reads thread pool (dfs.client.hedged.read.threadpool.size) is undersized.

  was:
When adding Hedged Reads metrics at https://issues.apache.org/jira/browse/HBASE-12220, hedgedReadOpsInCurThread was not included.

I wonder if there was any reason to not include them. If not, I will provide pull request to include them soon.


> Add hedgedReadOpsInCurThread metric
> -----------------------------------
>
>                 Key: HBASE-24994
>                 URL: https://issues.apache.org/jira/browse/HBASE-24994
>             Project: HBase
>          Issue Type: Improvement
>          Components: metrics
>            Reporter: Javier Akira Luca de Tena
>            Assignee: Javier Akira Luca de Tena
>            Priority: Minor
>
> When adding Hedged Reads metrics at https://issues.apache.org/jira/browse/HBASE-12220, hedgedReadOpsInCurThread was not included.
> I wonder if there was any reason to not include them. If not, I will provide pull request to include them soon.
> This metric is very useful the determine if the hedged reads thread pool (dfs.client.hedged.read.threadpool.size) is undersized.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)