[MDEV-10974] WSREP and multi-master replication: slave threads hang waiting for WSREP ready state Created: 2016-10-07 Updated: 2017-04-20 Resolved: 2017-04-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Replication, wsrep |
| Affects Version/s: | 10.1.17, 10.1.18 |
| Fix Version/s: | 10.1.22 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Alex/AT | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | hang | ||
| Environment: |
CentOS 7 (XenServer VM), vanilla MariaDB 10.1 RPM distribution |
||
| Sprint: | 10.1.20 |
| Description |
|
During start of MariaDB server, slave SQL threads wait for WSREP to reach ready state and only then start applying. With Galera Cluster and multi-master replication to it set up, multiple threads wait for the state. And then, basically, on MariaDB restarts, only one thread (seems to be more or less random) gets ready state notification. All other slave threads hang waiting (they are retrieving events to relay logs, but SQL threads are shown running and are really not applying anything, exec position does not increase). Any STOP SLAVE command or MariaDB server shutdown hangs then as well waiting for the hung slave threads to stop. |
| Comments |
| Comment by Nirbhay Choubey (Inactive) [ 2016-11-30 ] |
|
Alex/AT Could you describe the topology that you are trying out and also |
| Comment by Alex/AT [ 2017-03-21 ] |
|
Seems to be resolved in 10.1.22 with the STOP SLAVE deadlock fix. |