[
https://issues.apache.org/jira/browse/HBASE-8965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711715#comment-13711715
]
stack commented on HBASE-8965:
------------------------------
I wonder if this is to be believed:
- Thread LEAK? -, OpenFileDescriptor=335 (was 334) - OpenFileDescriptor LEAK?
-, MaxFileDescriptor=65536 (was 65536), SystemLoadAverage=869 (was 859) -
SystemLoadAverage LEAK? -, ProcessCount=85 (was 85), AvailableMemoryMB=4223
(was 4332), ConnectionCount=4 (was 4)
Descriptors are up against the limit and load is 870. That could do it.
[[email protected]] Any input here? After first test
testCreateAndDeleteTable runs, there are more threads afloat:
2013-07-17 20:54:50,781 INFO [pool-1-thread-1] hbase.ResourceChecker(171):
after: rest.client.TestRemoteAdmin#testCreateAnDeleteTable Thread=184 (was 161)
Going to disable this test for now.
> TestRemoteAdmin.testClusterStatus fails
> ---------------------------------------
>
> Key: HBASE-8965
> URL: https://issues.apache.org/jira/browse/HBASE-8965
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: stack
> Fix For: 0.95.2
>
> Attachments: 8965.txt
>
>
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/606/testReport/org.apache.hadoop.hbase.rest.client/TestRemoteAdmin/testClusterStatus/
> and here:
> http://54.241.6.143/job/HBase-0.95/597/org.apache.hbase$hbase-server/testReport/junit/org.apache.hadoop.hbase.rest.client/TestRemoteAdmin/testClusterStatus/
> Looks like tests running out of order with a table being deleted before this
> test runs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
