[
https://issues.apache.org/jira/browse/HBASE-23795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048462#comment-17048462
]
Mark Robert Miller commented on HBASE-23795:
--------------------------------------------
So, after getting to know the tests more individually, they did not match up
with experience of trying to run the test suite. So I jumped ahead a bit.
I reduced resources and improvement. But the test suite still did not make
sense.
I started shutting down resources and resolving deadlock or deadlock like
situations on shutdown.
I removed System.exit type calls that not appropriate for Junit tests and kill
JVM’s on us.
Again, I saw improvements but the test runs still didn’t make sense.
So I started hacking and providing higher limits to find out why nothing made
sense.
In the end, lots of connections are fired up, few are closed, unless you run
the tests fairly slowly, you will bed DOS attacked by them.
The worst of the leaks appears to be within the rpc client.
These tests are much faster, the rest of the flakies become conquerable,
running tests with more parallel JVMs and even in the same JVM is now not that
difficult, though some of the code does make it a little exercise. Good news
all around.
> Enable all tests to be run in parallel on reused JVMs.
> ------------------------------------------------------
>
> Key: HBASE-23795
> URL: https://issues.apache.org/jira/browse/HBASE-23795
> Project: HBase
> Issue Type: Wish
> Reporter: Mark Robert Miller
> Priority: Major
>
> I'd like to be able to run HBase tests in under 30-40 minutes on good
> parallel hardware.
> It will require some small changes / fixes for that wish to come true.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
