hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nkeywal (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4847) Activate single jvm for small tests on jenkins
Date Sun, 04 Dec 2011 09:57:40 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162328#comment-13162328
] 

nkeywal commented on HBASE-4847:
--------------------------------

We're leaking threads in the tests actually. It seems that hadoop-qa is less tolerant than
my env; but the issue is real.

Here is a snapshot.

{noformat}
main.logSyncer
main.logSyncer
main.logSyncer
Signal Dispatcher
main.logSyncer
main.logSyncer
Finalizer
main.logSyncer
main.logSyncer
mockserver.example.org,1234,-1.splitLogManagerTimeoutMonitor
LRU Statistics #0
Reference Handler
main.logSyncer
main
main.logSyncer
mockserver.example.org,1234,-1.splitLogManagerTimeoutMonitor
main.logSyncer
LruBlockCache.EvictionThread
main.logSyncer
main.logSyncer
main.logSyncer
main.logSyncer
main.logSyncer
main.logSyncer
main.logSyncer
{noformat}
 
main.logSyncer leaks when you don't close the hlog linked to a region. Many tests closes the
region but not the hlog, while some other closes nothing. The patch v12 fixes some leaks,
not all of them.

I will try anyway to limit it it to something not too large if not it won't be possible to
keep in sync with trunk...

                
> Activate single jvm for small tests on jenkins
> ----------------------------------------------
>
>                 Key: HBASE-4847
>                 URL: https://issues.apache.org/jira/browse/HBASE-4847
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, test
>    Affects Versions: 0.94.0
>         Environment: build
>            Reporter: nkeywal
>            Assignee: nkeywal
>            Priority: Minor
>         Attachments: 4847_all.v10.patch, 4847_all.v10.patch, 4847_all.v10.patch, 4847_all.v11.patch,
4847_all.v11.patch, 4847_all.v12.patch, 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch,
4847_all.v6.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_all.v7.patch,
4847_all.v8.patch, 4847_all.v8.patch, 4847_all.v9.patch, 4847_pom.patch, 4847_pom.v2.patch,
4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch
>
>
> This will not revolutionate performances alone. We will win between 1 to 4 minutes.
> But we win as well:
>  - it's a step for parallelizing the tests
>  - new tests are less expensive as they do not create a new jvm: it's a continuous win
>  - it will allow to push it on dev env while having the same env on dev & on build,
and 3 minutes are 10% of small + medium tests execution time.
> I will do a few "submit patch" to see if it works well before asking for the real commit.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message