[
https://issues.apache.org/jira/browse/HBASE-16289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399341#comment-15399341
]
stack commented on HBASE-16289:
-------------------------------
I used to think that these messages would happen when the jenkins slave had run
amok and was filled with zombie processes consuming all resources. I wonder if
that the case here. There used to be a printout of processes when a job ran so
you could get an idea of the environment. I should add such a thing to yetus
@busbey ? In the jenkins UI it also used to show what else was running on the
machine. Maybe a neighbour process stole all resources?
But yes, agree, not this patch. Thanks for digging in [~carp84]
> 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
> Fix For: 2.0.0, 1.3.0, 1.1.6, 1.2.3
>
> 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)
