[ https://issues.apache.org/jira/browse/CASSANDRA-14558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534660#comment-16534660 ]
Stefan Podkowinski commented on CASSANDRA-14558: ------------------------------------------------ [~KurtG], can you elaborate a bit on why you think this isn't an actual issue, as you mentioned in #dev? Shouldn't we have "Log-watching thread exiting" messages in the log, if the behaviour isn't broken in a way as described in this ticket? > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org