[
https://issues.apache.org/jira/browse/HBASE-16289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398634#comment-15398634
]
Yu Li commented on HBASE-16289:
-------------------------------
Yes sir, taking usage of the already-recorded regions/servers information of
ongoing tasks in AsyncProcess makes the logging easier. :-)
I also have no idea about the hadoopcheck failures, and checking the UT result
it only ran 115 cases, which is abnormal. Maybe we could wait for the result of
next run.
> 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
> Assignee: Yu Li
> Priority: Critical
> Labels: beginner
> Attachments: HBASE-16289.patch, 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)
