[
https://issues.apache.org/jira/browse/CASSANDRA-17629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539025#comment-17539025
]
Brandon Williams commented on CASSANDRA-17629:
----------------------------------------------
This isn't actually as I first thought with CASSANDRA-17606 a schema issue, or
at least not one there is control over. This is happening when 2.2 is
[checking for existing
roles|https://github.com/apache/cassandra/blob/cassandra-2.2/src/java/org/apache/cassandra/auth/CassandraRoleManager.java#L388]
and the schema for them hasn't been loaded on the receiving node yet.
On node3:
{noformat}
WARN [MessagingService-Incoming-/127.0.0.1] 2022-05-18 18:36:04,397
IncomingTcpConnection.java:100 - UnknownColumnFamilyException reading from
socket; closing
org.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.
{noformat}
On node2, about a second later:
{noformat}
INFO [OptionalTasks:1] 2022-05-18 18:36:05,660 CassandraRoleManager.java:378 -
Created default superuser role 'cassandra'
{noformat}
If anything, this is a bug in 2.2 but it's not relevant now so I've added this
to the ignore fixture
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17629]. I'll
check back when the 500 circle runs that are going
[here|https://app.circleci.com/pipelines/github/driftx/cassandra/489/workflows/ee33f6d5-e4a9-4021-aed5-a92a32ced896]
finish.
> 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
> Assignee: 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: [email protected]
For additional commands, e-mail: [email protected]
