accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-3429) Tests leaking LRUBlockCache threads
Date Mon, 06 Apr 2015 02:02:12 GMT


Josh Elser updated ACCUMULO-3429:
    Fix Version/s:     (was: 1.7.0)

> Tests leaking LRUBlockCache threads
> -----------------------------------
>                 Key: ACCUMULO-3429
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>            Reporter: Josh Elser
>            Priority: Minor
>              Labels: newbie
>             Fix For: 1.8.0, 1.7.1
> Been having sporadic issues since upgrading past ~1.7.0_51 with SIGSEGVs on my Mac. Poked
through the JVM error log that is created and noticed that, when the JVM crashed running the
core/ unit tests, we had a few threads sitting around.
> {noformat}
>   0x00007fd0cc10e000 JavaThread "LRUBlockCacheStats 1" daemon [_thread_blocked, id=29955,
>   0x00007fd0cd846000 JavaThread "LruBlockCache.EvictionThread" daemon [_thread_blocked,
id=29443, stack(0x000000011b3df000,0x000000011b4df000)]
>   0x00007fd0cc931800 JavaThread "LRUBlockCacheStats 1" daemon [_thread_blocked, id=28931,
>   0x00007fd0cda01000 JavaThread "LruBlockCache.EvictionThread" daemon [_thread_blocked,
id=28419, stack(0x000000011b1d9000,0x000000011b2d9000)]
>   0x00007fd0cab91800 JavaThread "LRUBlockCacheStats 1" daemon [_thread_blocked, id=27907,
>   0x00007fd0ca21b000 JavaThread "LruBlockCache.EvictionThread" daemon [_thread_blocked,
id=27395, stack(0x000000011ace4000,0x000000011ade4000)]
>   0x00007fd0ca1f2000 JavaThread "LRUBlockCacheStats 1" daemon [_thread_blocked, id=26883,
>   0x00007fd0cc983000 JavaThread "LruBlockCache.EvictionThread" daemon [_thread_blocked,
id=26371, stack(0x0000000119bd9000,0x0000000119cd9000)]
>   0x00007fd0ca00e000 JavaThread "LRUBlockCacheStats 1" daemon [_thread_blocked, id=25859,
>   0x00007fd0caa91800 JavaThread "LruBlockCache.EvictionThread" daemon [_thread_blocked,
id=25347, stack(0x0000000119744000,0x0000000119844000)]
>   0x00007fd0caa90800 JavaThread "LRUBlockCacheStats 1" daemon [_thread_blocked, id=24835,
>   0x00007fd0ca9dd800 JavaThread "LruBlockCache.EvictionThread" daemon [_thread_blocked,
id=24323, stack(0x000000011953e000,0x000000011963e000)]
>   0x00007fd0cc085800 JavaThread "LRUBlockCacheStats 1" daemon [_thread_blocked, id=23811,
>   0x00007fd0cab88000 JavaThread "LruBlockCache.EvictionThread" daemon [_thread_blocked,
id=23299, stack(0x00000001192bd000,0x00000001193bd000)]
>   0x00007fd0caa20800 JavaThread "LRUBlockCacheStats 1" daemon [_thread_blocked, id=22787,
>   0x00007fd0caa62000 JavaThread "LruBlockCache.EvictionThread" daemon [_thread_blocked,
id=22275, stack(0x00000001190b2000,0x00000001191b2000)]
> {noformat}
> They're daemon threads which is good, but we can probably do better and make sure the
test that starts them actually cleans them up, too. Need to identify the test which is causing
them to be created (likely some test that does something with the LRUBlockCache).

This message was sent by Atlassian JIRA

View raw message