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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/07/29 03:28:20 UTC

[jira] [Updated] (HBASE-15931) Add log for long-running tasks in AsyncProcess

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

stack updated HBASE-15931:
--------------------------
    Component/s: Operability

> Add log for long-running tasks in AsyncProcess
> ----------------------------------------------
>
>                 Key: HBASE-15931
>                 URL: https://issues.apache.org/jira/browse/HBASE-15931
>             Project: HBase
>          Issue Type: Improvement
>          Components: Operability
>            Reporter: Yu Li
>            Assignee: Yu Li
>             Fix For: 2.0.0, 1.4.0, 0.98.20
>
>         Attachments: HBASE-15931.patch
>
>
> Currently if there's any long-tail tasks in a multi-action request like triggered by {{BufferedMutatorImpl#backgroundFlushCommits}}, we could see logging message like below
> {noformat}
> 2016-05-31 09:36:55,461 INFO [Thread-16] org.apache.hadoop.hbase.client.AsyncProcess: #28, waiting for some tasks to finish. Expected max=0, tasksInProgress=1
> {noformat}
> but there's no way to know detail of this long-tail, such as which table/region it's accessing. This JIRA aims at adding such log for easier debugging.



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