[
https://issues.apache.org/jira/browse/HBASE-16289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398849#comment-15398849
]
Yu Li commented on HBASE-16289:
-------------------------------
Checking the IT result, the failure happens against JDK7 and from the output we
could observed below output:
{noformat}
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create GC thread. Out of system resources.
# An error report file with more information is saved as:
#
/home/jenkins/jenkins-slave/workspace/HBase-1.3-IT/it.test/IntegrationTestBigLinkedList/jdk/latest1.7/label/yahoo-not-h2/hbase-it/hs_err_pid22165.log
{noformat}
So it should be an env problem, and since test against JDK8 succeeded, the new
commit(s) should be OK.
> 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)
