[
https://issues.apache.org/jira/browse/CASSANDRA-18707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769660#comment-17769660
]
Ekaterina Dimitrova edited comment on CASSANDRA-18707 at 9/27/23 2:59 PM:
--------------------------------------------------------------------------
Reasons why I am not convinced we should raise it everywhere:
- 4.0 is a stable branch where we do not see many changes or this type of
failures (so let's say it would be probably just with/without - it is ok)
- we see this timeout with a specific test, and not with many, which makes it
suspicious.
- if anyone gets back to the issue, they will find the previous conversation on
this ticket and not waste time from scratch.
In Python DTests we opted to raise the timeout per tests or in create_cf.
However it seems the majority opted in for 120, so let's just accept your
suggestion here and move on. I guess that the suspicious test will pop in again
if there is something bigger.
+1, assuming the patch is the same on all branches and there is green CI per
branch
was (Author: e.dimitrova):
Reasons why I am not convinced we should raise it everywhere:
- 4.0 is a stable branch where we do not see many changes or this type of
failures (so let's say it would be probably just with/without - it is ok)
- we see this timeout with a specific test, and not with many, which makes it
suspicious.
- if anyone gets back to the issue, they will find the previous conversation on
this ticket and not waste time from scratch.
In Python DTests we opted to raise the timeout per tests or in create_cf.
However it seems the majority opted in for 120, so let's just accept your
suggestion here and move on. I guess that the suspicious test will pop in again
if there is something bigger.
+1
> 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
