Re: COMMERCIAL:Re: COMMERCIAL:Re: COMMERCIAL:Re: system_schema.tables id and table uuid on disk mismatch

2024-01-18 Thread Bowen Song via user
Without knowing the cause of the issue, it's hard to tell what are the correct steps to recover from it. I would recommend you have a look at the logs and figure out what was the cause of the issue, and then make a recovery plan and also put preventive measure in place to stop it from

Re: COMMERCIAL:Re: COMMERCIAL:Re: COMMERCIAL:Re: system_schema.tables id and table uuid on disk mismatch

2024-01-18 Thread ENES ATABERK
ok thank you! What do you think about the following approach: 1. creating empty correct table id directories in linux filesystem with respect to the system_schema.tables id column 2. importing data with nodetool import from incorrect directory 3. removing the incorrect directory

Re: COMMERCIAL:Re: COMMERCIAL:Re: system_schema.tables id and table uuid on disk mismatch

2024-01-18 Thread Bowen Song via user
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 ticket for it. On 18/01/2024 14:44, ENES ATABERK wrote:

Re: COMMERCIAL:Re: COMMERCIAL:Re: system_schema.tables id and table uuid on disk mismatch

2024-01-18 Thread ENES ATABERK
It has same mismatch id in all nodes not just one node. From: Bowen Song via user Sent: Thursday, January 18, 2024 3:18:11 PM To: user@cassandra.apache.org Cc: Bowen Song Subject: COMMERCIAL:Re: COMMERCIAL:Re: system_schema.tables id and table uuid on disk

Re: COMMERCIAL:Re: system_schema.tables id and table uuid on disk mismatch

2024-01-18 Thread Bowen Song via user
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, Thanks for

Re: COMMERCIAL:Re: system_schema.tables id and table uuid on disk mismatch

2024-01-18 Thread ENES ATABERK
Hi all, Thanks for your responses. The version is Cassandra 4.1.3 After I restarted all the nodes one-by-one cassandra created corrected-id folder and keep the incorrect one as you said. But then I cannot see the data from cqlsh it gives me no result. After i have imported the data from

Re: system_schema.tables id and table uuid on disk mismatch

2024-01-18 Thread Bowen Song via user
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

Re: system_schema.tables id and table uuid on disk mismatch

2024-01-18 Thread Štefan Miklošovič
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