[
https://issues.apache.org/jira/browse/CASSANDRA-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921549#comment-17921549
]
David Capwell commented on CASSANDRA-20248:
-------------------------------------------
CASSANDRA-20069 refactored jvm-dtest which caused this test to fail.
Alex/Benedict/I talked about it and the following is what we talked about
1) the change was trying to cleanup the logic where we try to find the right
cluster, and make sure we call JVMStabilityInspector correctly. This logic
basically tries to solve CASSANDRA-19515
2) the change to mark corruption as unhandled was not intentional, and
Alex/Benedict are +0 to going back to the old semantic.
3) CASSANDRA-20069 moved to using reflection to call JVMStabilityInspector
rather than Instance.uncaughtException, this can become an issue for upgrade
tests when and if that internal class has a API change... we should revert back
to using Instance.uncaughtException to avoid breaking upgrade tests in the
future
> Fix failing repair test
> ------------------------
>
> Key: CASSANDRA-20248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20248
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Accord
> Reporter: Alex Petrov
> Assignee: David Capwell
> Priority: Normal
> Time Spent: 1h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
