[CASSANDRA-14617] Corruption in schema changes due to clock jumps

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Component/s: Legacy/Core
• Severity: Normal
• Assignee: Unassigned
• Reporter: Garvit Juniwal
• Created: 01/Aug/18 21:35
• Updated: 16/Apr/19 09:29

Description

It seems like schema changes like CREATE/DROP TABLE can get swallowed or re-ordered if there are clock jumps on the host. I am able to reproduce this on version 3.0.9 by doing the following:

t = 10 CREATE  TABLE foo
manually set the host clock to t = 5
t = 5 DROP TABLE foo
.. let time advance ..
t = 11 table foo still exists in schema

There does not seem to be a way to either provide user timestamps or use light weight transactions for schema changes (at least not documented in to https://docs.datastax.com/en/cql/3.3/cql/cql_using/useInsertLWT.html or https://docs.datastax.com/en/cql/3.3/cql/cql_reference/cqlCreateTable.html)