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

Berenguer Blasi edited comment on CASSANDRA-17283 at 2/15/22, 11:25 AM:
------------------------------------------------------------------------

I also found:

bq. Wrong thread status, active threads unaccounted for: [Shutdown-checker]
bq. Wrong thread status, active threads unaccounted for: 
[cluster3-connection-reaper-0]

Where the first one googling a bit seems to be some jdk thread. The cluster 
connection reapears from the C* driver. They both seems benign and probably the 
fix is to add them to the list of exclusion of threads to check. These come up 
as we're invoking the _class_ directly, not the _tool_. Need to look a bit more 
though.



was (Author: bereng):
I also found:

bq. Wrong thread status, active threads unaccounted for: [Shutdown-checker]
bq. Wrong thread status, active threads unaccounted for: 
[cluster3-connection-reaper-0]

Where the first one googling a bit seems to be some jdk thread. The cluster 
connection reapears from the C* driver*. They both seems benign and probably 
the fix is to add them to the list of exclusion of threads to check. Need to 
look a bit more though.


> Failing test: UNIT 
> org.apache.cassandra.tools.BulkLoaderTest.testBulkLoader_WithArgs1
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17283
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17283
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/unit
>            Reporter: Josh McKenzie
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.x
>
>
> Intermittent failure: 
> [https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/org.apache.cassandra.tools/BulkLoaderTest/testBulkLoader_WithArgs1]
> h3. Error Message
> Wrong thread status, active threads unaccounted for: 
> [cluster2-connection-reaper-0]
> h3. Stacktrace
> junit.framework.AssertionFailedError: Wrong thread status, active threads 
> unaccounted for: [cluster2-connection-reaper-0] at 
> org.apache.cassandra.tools.OfflineToolUtils.assertNoUnexpectedThreadsStarted(OfflineToolUtils.java:106)
>  at 
> org.apache.cassandra.tools.BulkLoaderTest.testBulkLoader_WithArgs1(BulkLoaderTest.java:85)
>  at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method) at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> h3. Standard Output
> DEBUG [main] 2022-01-21 19:11:46,606 InternalLoggerFactory.java:63 - Using 
> SLF4J as the default logging framework DEBUG [main] 2022-01-21 19:11:46,634 
> PlatformDependent0.java:417 - -Dio.netty.noUnsafe: false DEBUG [main] 
> 2022-01-21 19:11:46,634 PlatformDependent0.java:897 - Java version: 8 DEBUG 
> [main] 2022-01-21 19:11:46,636 PlatformDependent0.java:130 - 
> sun.misc.Unsafe.theUnsafe: available DEBUG [main] 2022-01-21 19:11:46,636 
> PlatformDependent0.java:154 - sun.misc.Unsafe.copyMemory: available



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to