Hi, We have microservices that use Cassandra. Each instance, when started,
creates the required DB schema (and keeps a changelog). As instances can be
started at the same time, we use a row in a table as lock - insert into if not
exists using ttl. That all works without any issues.The problem is that the
table that contains the lock is also created by the applications using create
if not exists. Despite the name, Cassandra seems to have racing condition when
this statement is called concurrently - it ends up with multiple definitions of
a table with different table id. Any DDLs after that fail with configuration
exceptions. How does one clean up after that has happened?As a work around
we're creating table with explicit table id set (computed from the key space
and table name so that all nodes generate the same id. This kind of works but
feels like an ugly hack. Are there other options that you can think of that
only rely on Cassandra?CheersDimo
