Andres de la Peña created CASSANDRA-16878:
---------------------------------------------
Summary: Race in commit log replay can cause rejected mutations
Key: CASSANDRA-16878
URL: https://issues.apache.org/jira/browse/CASSANDRA-16878
Project: Cassandra
Issue Type: Bug
Reporter: Andres de la Peña
Assignee: Andres de la Peña
We don't force order in the execution of replayed mutations and hence a
mutation can move ahead of or behind a schema change it relies on (e.g.
added/removed column), which can then cause it to be rejected because of a
schema mismatch.
To fix this, we need to identify schema mutations and make sure the log
enforces their execution after all previous mutations have completed and before
anything following is started.
Schema mutations are
[flushed|https://github.com/apache/cassandra/blob/cassandra-4.0.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L1266-L1271]
after being applied, so this only would be a problem if the node abruptly
stops before flushing the schema mutation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
