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
streaming time.
However, if the table schema is different, this may cause a havoc.
On 18/01/2024 05:21, ENES ATABERK wrote:
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
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/2024 13:14, ENES ATABERK wrote:
Hi all,
Thank
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
ticket for it.
On 18/01/2024 14:44, ENES ATABERK wrote:
It has same mismatch id i
