Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.1.10
-
13 nodes running MariaDB 10.1.10 with Galera
This occurs with the shipping .9 version of the Galera library as well as the latest .14 version.
Layout:
DC1: 3 nodes
DC2: 3 nodes
DC3: 3 nodes
DC4: 3 nodes
DC5: 1 node
Each site minus DC5 has at least 4 async slaves hanging off a VIP, where only one of the 3 nodes at that site is active. (Priority LB method)13 nodes running MariaDB 10.1.10 with Galera This occurs with the shipping .9 version of the Galera library as well as the latest .14 version. Layout: DC1: 3 nodes DC2: 3 nodes DC3: 3 nodes DC4: 3 nodes DC5: 1 node Each site minus DC5 has at least 4 async slaves hanging off a VIP, where only one of the 3 nodes at that site is active. (Priority LB method)
Description
My 13 node cluster is used for DNS and therefor has a lot more reads than writes. The issue seems to stem from DNS slave nodes in each site which perform a lot of UPDATE statements on the same table. Each site has a VIP where only one of the 3 nodes at that site are active at one time. I will attach my error log and configuration file.