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

Ekaterina Dimitrova edited comment on CASSANDRA-19043 at 2/13/24 8:02 PM:
--------------------------------------------------------------------------

[~dcapwell] , am I right in saying we hit the problem you describe in 
CASSANDRA-19042 here? Repair does not finish:
{code:java}
java.util.concurrent.TimeoutException
    at 
org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:253)
    at 
org.apache.cassandra.repair.RepairJobTest.testValidationFailure(RepairJobTest.java:332)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
    at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
    at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
    at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
    at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
    at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
    at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
    at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
    at 
com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38)
    at 
com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11)
    at 
com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35)
    at 
com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:232)
    at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:55){code}


was (Author: e.dimitrova):
[~dcapwell] , am I right by saying that here we hit the problem you describe in 
CASSANDRA-19042?

> RepairJobTest fails with paxos_variant: v2
> ------------------------------------------
>
>                 Key: CASSANDRA-19043
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19043
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Consistency/Repair, Feature/Lightweight Transactions
>            Reporter: Branimir Lambov
>            Priority: Normal
>             Fix For: 4.1.x, 5.0-rc
>
>
> {{testEndToEndNoDifferences}} and {{testValidationFailure}} time out. The 
> paxos repair stage never completes --- it's does not appear to be properly 
> wired up (e.g. {{outboundSink}} returns before processing the PAXOS2-specific 
> cases).
> This happens for all three options of {{paxos_state_purging}} and both with 
> and without {{storage_compatibility_mode: NONE}}.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to