[
https://issues.apache.org/jira/browse/CASSANDRA-16681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351980#comment-17351980
]
Adam Holmberg commented on CASSANDRA-16681:
-------------------------------------------
Although I still think there is a race as described, more troubleshooting has
indicated that it is not the cause for this assertion error most times. It's
happening earlier on in the test when the threads would not be exiting. When it
does happen, there is always only a single tracked chunk that has not been
recycled a given time interval. It appears that the chunk is not being acquired
or cycled in any way after entering this state. Still digging on it, but if
anyone with more knowledge in the area wants to take a look, they are welcome.
> org.apache.cassandra.utils.memory.LongBufferPoolTest - tests are flaky
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-16681
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16681
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Adam Holmberg
> Priority: Normal
> Fix For: 4.0, 4.0-rc
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Jenkins history:
> [https://jenkins-cm4.apache.org/job/Cassandra-4.0/50/testReport/junit/org.apache.cassandra.utils.memory/LongBufferPoolTest/testPoolAllocateWithRecyclePartially/history/]
> Fails being run in a loop in CircleCI:
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/844/workflows/945011f4-00ac-4678-89f6-5c0db0a40169/jobs/5008
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
