[
https://issues.apache.org/jira/browse/HBASE-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171075#comment-16171075
]
Nick Dimiduk commented on HBASE-15931:
--------------------------------------
[~carp84]: FYI, please don't commit patches for long-ago release JIRA numbers.
Anything that's gone out in a release is supposed to be considered archived,
permanently frozen in time, a part of the historical record. Addendums to such
tickets make it difficult to parse that record. This one is minor, so fine to
let it be. Just for future reference...
We used to have a policy about closing all associated tickets once a release
ships. Seems a RM or two have been remiss in this practice, including yours
truly. Worth a revival thread on the dev list.
> 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
> Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.4.0, 0.98.20, 1.1.6, 1.2.3
>
> 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.4.14#64029)
