[
https://issues.apache.org/jira/browse/HBASE-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Li updated HBASE-15931:
--------------------------
Fix Version/s: 1.4.0
2.0.0
Release Note:
After HBASE-15931, we will log more details for long-running tasks in
AsyncProcess#waitForMaximumCurrentTasks every 10 seconds, including:
1. Table name will be included in the tasks status log
2. On which regionserver(s) the tasks are runnning will be logged when less
than hbase.client.threshold.log.details tasks left, by default 10.
3. Against which regions the tasks are running will be logged when less than 2
tasks left.
> 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)
