You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2025/01/27 21:35:00 UTC

[jira] [Commented] (CASSANDRA-19515) unhandled exception handling in jvm dtest may see errors from other clusters

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

David Capwell commented on CASSANDRA-19515:
-------------------------------------------

CASSANDRA-20069 made a change to use ThreadGroup to solve the problem, which should in theory be a better solution than this patch offered.

> unhandled exception handling in jvm dtest may see errors from other clusters
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-19515
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19515
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Test/dtest/java
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: NA
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> From time to time we see tests failing with unexpected errors during close, but this shouldn’t be possible because we ignore errors for instances that are shutting down…. In debugging it turns out that the errors are from different clusters, so we add to the unexpected error list even though it’s not from this cluster!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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