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
.apache.org *Cc:* 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

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 and

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

2024-01-18 Thread Bowen Song via user
AL: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 only applies to the one node situation.

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