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
:* Bowen Song *Subject:* COMMERCIAL:Re: COMMERCIAL:Re: 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

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

2024-01-18 Thread ENES ATABERK
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

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

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

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