[CASSANDRA-5904] Don't announce schema version until we've loaded the changes locally

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.9
• Severity: Low
• Assignee: Sylvain Lebresne
• Reporter: Sylvain Lebresne

Authors

Sylvain Lebresne

Reviewers

Aleksey Yeschenko

• Created: 20/Aug/13 10:21
• Updated: 16/Apr/19 09:32
• Resolved: 20/Aug/13 14:49

Description

Currently, we call updateSchemaAndAnnounce (which sets the schema version in the system table and announce it on gossip) in DefsTable.mergeSchema as soon as we've persisted the schema mutation but before we've actually loaded new/updated KS/CF locally. This makes it impossible to reliably check for schema agreement in a cluster as even if all nodes have the same version set in the system tables, you could still get an insert on a new table rejected because the table hasn't been loaded yet.