[
https://issues.apache.org/jira/browse/HBASE-16289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Li updated HBASE-16289:
--------------------------
Attachment: HBASE-16289.patch
Here's a straight forward patch taking usage of work done in HBASE-15931.
After the patch, logging will look like:
{noformat}
2016-06-23 17:07:18,759 INFO [Thread-1]
client.AsyncProcess$AsyncRequestFutureImpl(1601): #1, waiting for 1 actions to
finish on table: DUMMY_TABLE
2016-06-23 17:07:18,759 INFO [Thread-1] client.AsyncProcess(1720): Left over 1
task(s) are processed on server(s): [s1:1,1,1]
2016-06-23 17:07:18,759 INFO [Thread-1] client.AsyncProcess(1728): Regions
against which left over task(s) are processed:
[DUMMY_TABLE,DUMMY_BYTES_1,1.3fd12ea80b4df621fb15497ba75f7368.,DUMMY_TABLE,DUMMY_BYTES_2,2.924207e242e313d2e5491c625e0a296e.]
{noformat}
> AsyncProcess stuck messages need to print region/server
> -------------------------------------------------------
>
> Key: HBASE-16289
> URL: https://issues.apache.org/jira/browse/HBASE-16289
> Project: HBase
> Issue Type: Bug
> Components: Operability
> Reporter: stack
> Priority: Critical
> Labels: beginner
> Attachments: HBASE-16289.patch
>
>
> Fix these out of AsyncProcess...
> '2016-07-21 20:16:56.477 o.a.h.h.c.AsyncProcess [INFO] #13, waiting for 25
> actions to finish'
> They are totally opaque, when you see one, it means a request is ten seconds
> old at least. It is awkward to do but we should be able to emit region/server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
