The usual cause of this is the CQL statement CREATE TABLE ... and/or
CREATE TABLE ... IF NOT EXISTS were ran on two nodes in a short period
of time (i.e. before the schema is fully synced between the nodes). If
both tables (same name, different UUIDs) have data in them, fixing the
issue without losing data is a bit trickier. However, if any of them is
empty, you should be able to shutdown the node with the empty table,
delete the table's data folder on that node and then restart the node,
repeat this for all nodes with the empty table, and finally run a full
repair.
On 25/01/2022 07:32, Amandeep Srivastava wrote:
Hi,
We're running an embedded Janus graph on top of Cassandra. On starting
the graph, it creates certain tables in cassandra for its operation.
We noticed that there is an Id mismatch for one of the tables named
system_properties_lock i.e.
Id fetched from schema table of cass (SELECT keyspace_name,
table_name, id from system_schema.tables using cqlsh), and the path in
cassandra (/opt/Cassandra/data/Janus/system-properties_lock_-id), do
not match. IDs match for all other tables created by Janus except this
one.
Can someone please advice on what might be the cause of this mismatch
and how can it be fixed?
Regards,
Aman
