[
https://issues.apache.org/jira/browse/CASSANDRA-14558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535506#comment-16535506
]
Kurt Greaves commented on CASSANDRA-14558:
------------------------------------------
Turns out I was imagining a return statement when I glanced quickly yesterday.
Patch is fine and fixes the described issue, but not sure why I'm still getting
the same errors after applying the patch. I'll do a couple more runs and see if
it's something environment related.
> dtest: log-watching thread leak and thread starvation
> -----------------------------------------------------
>
> Key: CASSANDRA-14558
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14558
> Project: Cassandra
> Issue Type: Bug
> Components: Testing
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Priority: Major
>
> We get occasional build timeouts on b.a.o after pytest becomes unresponsive
> for over 20 minutes. This will result in a thread dump like this one:
> [https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-2.2-dtest/117/consoleFull]
> If you look for "Log-watching thread starting" messages and the dump, it
> becomes quite obvious whats the issue here.
> I had a quick look at the python3 / pytest related changes in CASSANDRA-14134
> and it seems that some of the handling around dtest_setup's
> {{log_watch_thread}} var has been changed in a way that would prevent
> eventually yielding the allocated thread.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
