Garvit Juniwal created CASSANDRA-14617: ------------------------------------------
Summary: Corruption in schema changes due to clock jumps Key: CASSANDRA-14617 URL: https://issues.apache.org/jira/browse/CASSANDRA-14617 Project: Cassandra Issue Type: Bug Reporter: Garvit Juniwal 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) -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org