:
system_schema.tables id and table uuid on disk mismatch
I know dropping a table and then creating a new table with the same
name can lead to that result, which is expected. If that wasn't what
happened, it may be a bug in Cassandra. If you can reproduce the
behaviour, you should raise a Jira
afterwards
From: Bowen Song via user
Sent: Thursday, January 18, 2024 5:34:57 PM
To: user@cassandra.apache.org
Cc: Bowen Song
Subject: COMMERCIAL:Re: COMMERCIAL:Re: COMMERCIAL:Re: system_schema.tables id
and table uuid on disk mismatch
I know dropping a table
: system_schema.tables id and
table uuid on disk mismatch
Was the table ID mismatching only on one node or all nodes?
Mismatching on one node is usually the result of a racing condition,
but on all nodes isn't. The solution I mentioned earlier only applies
to the one node situation.
On 18/01
OMMERCIAL:Re: system_schema.tables id and table uuid on disk mismatch
It sounds like you have done some concurrent table creation/deletion in the
past (e.g. CREATE TABLE IF NOT EXISTS from multiple clients), which resulted in
this mismatch. After you restarted the node, Cassandra corrected it by
discarding the
and table uuid on
disk mismatch
It sounds like you have done some concurrent table creation/deletion
in the past (e.g. CREATE TABLE IF NOT EXISTS from multiple clients),
which resulted in this mismatch. After you restarted the node,
Cassandra corrected it by discarding the old table ID and any data
cannot see any data before
nodetool import.
Thanks again.
From: Bowen Song via user
Sent: Thursday, January 18, 2024 1:17:11 PM
To: user@cassandra.apache.org
Cc: Bowen Song
Subject: COMMERCIAL:Re: system_schema.tables id and table uuid on disk mismatch
It sounds like you have done some concurrent table creation/deletion in
the past (e.g. CREATE TABLE IF NOT EXISTS from multiple clients), which
resulted in this mismatch. After you restarted the node, Cassandra
corrected it by discarding the old table ID and any data associated with
it. This
Hi,
what Cassandra version are you on? I do not see this behaviour in 5.0-beta.
When I create a table, its id will match the id part of table directory on
the disk.
Regards
On Thu, Jan 18, 2024 at 8:49 AM ENES ATABERK
wrote:
> Hi all,
>
> we have detected that table-uuid in linux file
Hi all,
we have detected that table-uuid in linux file directory is different from
system_schema.tables id.
I have executed nodetool describe cluster and see only one schema version in
the cluster.
How we can fix this issue do anyone has any idea? Restarting the nodes only
create a new empty
