Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
Description
Galera Cluster version 3, has strict inconsistency policy: all transaction replication errors cause emergency abort for all nodes detecting the inconsistency.
Galera Cluster 4 has more sophisticated inconsistency strategy where cluster runs inconsistency voting protocol and optimizes the way cluster reacts to detected inconsistency. With consistency voting, Galera Cluster can mitigate the harm of inconsistency for the cluster. In the best case, only one node has to abort, and majority can continue operating normally However, if the database has been inconsistent, for indefinitely long period, and application business logic may have been hurt
Attachments
Issue Links
- is part of
-
MDEV-16405 Merge Galera 4 changes from mariaDB_wsrep to 10.4
- Closed