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

Berenguer Blasi commented on CASSANDRA-18707:
---------------------------------------------

bq. 4.0 is a stable branch where we do not see many changes

Correct. The problem is that we have no insight as to what is happening in 
jenkins at the time. It might hit it as well

bq. we see this timeout with a specific test, and not with many, which makes it 
suspicious.

I disagree here. I have seen schema changes many times go over 60s in jenkins. 
That was a common scenario when we were on the 4.0 flaky fixing frenzy and 
that's why at the time I did already propose to raise timeouts already. That 
was declined and I found myself debugging through logs the same problem 2 or 3 
extra times. This is just another one.

bq. not waste time from scratch

Correct. But you you just have an indication of what have happened. You still 
have to wade through logs to confirm it is indeed the same scenario.

bq. In Python DTests we opted to raise the timeout

Correct and I think it was a good move. I will change the 140s to 120s for 
consistency and OCD lol

Thanks I'll put PRs up


> Test failure: 
> junit.framework.TestSuite.org.apache.cassandra.distributed.test.CASMultiDCTest-.jdk11
>  
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18707
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18707
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/dtest/java
>            Reporter: Ekaterina Dimitrova
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>         Attachments: TESTS-TestSuites.xml.xz
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit.framework/TestSuite/org_apache_cassandra_distributed_test_CASMultiDCTest__jdk11/]
> h3.  
> {code:java}
> Error Message
> Schema agreement not reached. Schema versions of the instances: 
> [ef1c8e05-a06d-388d-a46d-53cc22a94762, 6c386108-1805-3985-b48e-8016012a0207, 
> 6c386108-1805-3985-b48e-8016012a0207, ef1c8e05-a06d-388d-a46d-53cc22a94762]
> Stacktrace
> java.lang.IllegalStateException: Schema agreement not reached. Schema 
> versions of the instances: [ef1c8e05-a06d-388d-a46d-53cc22a94762, 
> 6c386108-1805-3985-b48e-8016012a0207, 6c386108-1805-3985-b48e-8016012a0207, 
> ef1c8e05-a06d-388d-a46d-53cc22a94762] at 
> org.apache.cassandra.distributed.impl.AbstractCluster$ChangeMonitor.waitForCompletion(AbstractCluster.java:907)
>  at 
> org.apache.cassandra.distributed.impl.AbstractCluster.lambda$schemaChange$8(AbstractCluster.java:836)
>  at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96) at 
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61) at 
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71) at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>  at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>  at 
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
>  at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
>  



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

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

Reply via email to