[
https://issues.apache.org/jira/browse/CASSANDRA-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-15450:
--------------------------------------
Test and Documentation Plan:
Patch located here: https://github.com/apache/cassandra/pull/397
Replicated the issue in IntelliJ by selecting {code}GossipSettlesTest{code} and
{code}FailingRepairTest{code} and calling run. Before this patch,
FailingRepairTest hangs until timeout, it never sees the jvm kill attempt (went
to the wrong host); after this patch the correct host gets killed
Status: Patch Available (was: Open)
> in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the
> wrong instance, it uses cluster generation when it should be using the
> instance id
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-15450
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15450
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In AbstractCluster.uncaughtExceptions, we attempt to get the instance from
> the class loader and used the “generation”. This value is actually the
> cluster id, so causes tests to fail when multiple tests share the same JVM;
> it should be using the “id” field which represents the instance id relative
> to the cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
