[CASSANDRA-18040] Avoid schema mismatch problems on memtable API misconfiguration

• Type: Improvement
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 4.1-rc1, 4.1, 5.0-alpha1, 5.0
• Component/s: Cluster/Schema
• Change Category: Operability
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://github.com/apache/cassandra/pull/2010 (4.1) and https://github.com/apache/cassandra/pull/2011 (master)

Test and Documentation Plan

Includes in-jvm dtest.

• Assignee: Branimir Lambov
• Reporter: Branimir Lambov

Authors

Branimir Lambov

Reviewers

Caleb Rackliffe

• Created: 14/Nov/22 10:51
• Updated: 12/Sep/23 13:02
• Resolved: 16/Nov/22 08:43

Description

The memtable API requires a definition of the memtable configuration to exist in cassandra.yaml. If that is not the case when a schema change is received from another node, this can cause the node to reject the schema change and behave incorrectly.

To fix this, a node should only fail to construct a memtable when it is validating CREATE or ALTER statements, but should fall back to default when it receives invalid configuration selections in the schema.

Issue Links

• is caused by: CASSANDRA-17034 CEP-11: Memtable API implementation