hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15931) Add log for long-running tasks in AsyncProcess
Date Thu, 02 Jun 2016 05:51:59 GMT

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

Hudson commented on HBASE-15931:
--------------------------------

FAILURE: Integrated in HBase-1.4 #188 (See [https://builds.apache.org/job/HBase-1.4/188/])
HBASE-15931 Add log for long-running tasks in AsyncProcess (liyu: rev 36bb496e4809f1ae3146fb93439f4531d7fea657)
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/BufferedMutatorImpl.java
* hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestAsyncProcess.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncProcess.java


> 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
>            Reporter: Yu Li
>            Assignee: Yu Li
>             Fix For: 2.0.0, 1.4.0
>
>         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)

Mime
View raw message