[CASSANDRA-5025] Schema push/pull race

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.1.8
• Severity: Low
• Assignee: Jonathan Ellis
• Reporter: Jonathan Ellis

Authors

Jonathan Ellis

Reviewers

Pavel Yaskevich

• Created: 04/Dec/12 17:52
• Updated: 16/Apr/19 09:32
• Resolved: 07/Dec/12 21:45

Description

When a schema change is made, the coordinator pushes the delta to the other nodes in the cluster. This is more efficient than sending the entire schema. But the coordinator also announces the new schema version, so the other nodes' reception of the new version races with processing the delta, and usually seeing the new schema wins. So the other nodes also issue a pull to the coordinator for the entire schema.

Thus, schema changes tend to become O in the number of KS and CF present.

Issue Links

• is related to: CASSANDRA-8387 Schema inconsistency (cached vs schema_columnfamilies)
• relates to: CASSANDRA-13061 C* driver hangs forever in case of concurrent CREATE TABLE IF NOT EXISTS