Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Not a Bug
-
10.11.3, 10.3.39
-
Linux Debian 10 (Primary), Linux Debian 12 (Replica)
Description
I just got a major server crash, needing to reboot everything.
This server is hosting a MariaDB primary database replicated elsewhere.
After the crash, three database tables got corrupted, needing REPAIR TABLE.
When repairing, the process list shows “Repair by sorting” during the repair.
This needed time, but it worked.
What I found very surprising was that the Replicas also began “Repair by sorting”, likely for the same tables.
Is it normal that the replication is so closely linked to the original that the damaged tables in the Primary are also considered damaged in the Replicas?