[
https://issues.apache.org/jira/browse/CASSANDRA-21216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072452#comment-18072452
]
Andrés Beck-Ruiz commented on CASSANDRA-21216:
----------------------------------------------
Why wouldn't we also need to set {{savedNextKey}} to {{{}null{}}}? Could the
leftover {{savedNextKey}} enter the next BTree that is built by the stale
{{{}FastBuilder{}}}?
For example, {{hasOverflow}} would return true even though the next caller
should be retrieving a clean builder. This would eventually lead to
{{redistributeOverflowAndDrain()}} where we [populate the newLeaf with the
{{savedNextKey.}}|https://bbgithub.dev.bloomberg.com/NoSQL-Platform/cassandra/blob/internal-cassandra-4.1.10/src/java/org/apache/cassandra/utils/btree/BTree.java#L2671]
> ClassCastException thrown on read and write paths after schema modification
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-21216
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21216
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Isaac Reath
> Assignee: Andrés Beck-Ruiz
> Priority: Normal
> Fix For: 4.1.x
>
> Attachments: ClassCastException-Read.txt,
> ClassCastException-Writes-1.txt
>
>
> After a schema modification on a cluster serving reads and writes, we have
> noticed that it is possible to see ClassCastException being thrown when
> comparing clustering keys in a few codepaths (see attached stacktraces).
> After a schema modification, we see regular ClassCastExceptions happening on
> both the read and write paths.
> The table in question is a very wide table, ~4200 columns and it occurred
> originally on a cluster with 30 nodes running 4.1.3.
> I've been able to reproduce it on a 3 node cluster running 4.1.10 with a
> single data center that is doing ~60 req/sec and frequent concurrent schema
> modifications. It appears to be a race as it doesn't happen on every schema
> change, but will occur at a rate of roughly 1/200 schema changes while the
> read/write workload is ongoing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
