Hi Erick
Thank you very much for your friendly note.
ERROR [AntiEntropyStage:1] 2020-04-04 13:57:09,614
RepairMessageVerbHandler.java:177 - Table with id
21a3fa90-74c7-11ea-978a-b556b0c3a5ea was dropped during prepare phase of repair
cassandra@cqlsh:system_schema> select keyspace_name,table_name
This is confirmation that you have a schema disagreement in your cluster:
- 21a3fa90-74c7-11ea-978a-b556b0c3a5ea = Friday, April 3 05:07:44 PT
- 830028a0-7584-11ea-a277-bdf3d1289bdd = Friday, April 3 01:24:18 PT
The schema on the node where you ran that query has an older version of the
tab
Thank you very much for your friendly note.
ERROR [AntiEntropyStage:1] 2020-04-04 13:57:09,614
RepairMessageVerbHandler.java:177 - Table with id
21a3fa90-74c7-11ea-978a-b556b0c3a5ea was dropped during prepare phase of repair
cassandra@cqlsh:system_schema> select keyspace_name,table_name,id f
Is it possible someone else dropped then recreated the logtabl table? Also,
did you confirm that the missing table ID matches the ID of logtabl?
On a friendly note, there are a number of users here like me who respond to
questions on the go. I personally find it difficult to read screenshots on
my
And from your review of the logs, what was the cause of the repair
failures? Because that's likely to yield clues on the root cause. Cheers!
