You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/05/16 12:28:00 UTC
[jira] [Commented] (CASSANDRA-17629) Fix flaky dtest - upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_3_11_X.test_rolling_upgrade
[ https://issues.apache.org/jira/browse/CASSANDRA-17629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537513#comment-17537513 ]
Ekaterina Dimitrova commented on CASSANDRA-17629:
-------------------------------------------------
Hm, I think 100 runs of the test to confirm being not flaky anymore is low. Normally I test at least 500
> Fix flaky dtest - upgrade.upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_3_11_X.test_rolling_upgrade
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17629
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17629
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Brandon Williams
> Priority: Normal
> Fix For: 4.0.x, 4.1-beta, 4.1.x
>
>
> {code}
> Error Message
> test teardown failure
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors: [[node3] 'WARN [MessagingService-Incoming-/127.0.0.2] 2022-05-14 07:23:56,540 IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from socket; closing\norg.apache.cassandra.db.UnknownColumnFamilyException: Got slice command for nonexistent table system_auth.roles. If the table was just created, this is likely due to the schema not being fully propagated. Please wait for schema agreement on table creation.\n\tat org.apache.cassandra.db.SliceFromReadCommandSerializer.deserialize(SliceFromReadCommand.java:184) ~[apache-cassandra-2.2.19.jar:2.2.19]\n\tat org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:158) ~[apache-cassandra-2.2.19.jar:2.2.19]\n\tat org.apache.cassandra.db.ReadCommandSerializer.deserialize(ReadCommand.java:132) ~[apache-cassandra-2.2.19.jar:2.2.19]\n\tat org.apache.cassandra.net.MessageIn.read(MessageIn.java:99) ~[apache-cassandra-2.2.19.jar:2.2.19]\n\tat org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:200) ~[apache-cassandra-2.2.19.jar:2.2.19]\n\tat org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:177) ~[apache-cassandra-2.2.19.jar:2.2.19]\n\tat org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91) ~[apache-cassandra-2.2.19.jar:2.2.19]']
> {code}
> I thought we might have fixed this with CASSANDRA-17606, but it appears not.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org