[MDEV-22707] galera got stuck after flush tables Created: 2020-05-26 Updated: 2021-04-19 Resolved: 2020-10-27 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 10.1.38, 10.3.23 |
| Fix Version/s: | 10.2.35, 10.3.26 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Allen Lee (Inactive) | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
MariaDB Server MariaDB-10.1.38 & Galera cluster 3.29 |
||
| Attachments: |
|
| Description |
|
Customer created test case to simulate production stuck when running percona backup. 0) ./dealock.sh <user> <password> Once this script finished, both node2 and node3 got stuck so nothing could be run until restarting all nodes. But the interesting thing is that node2 and node3 do not stuck if node1 is in wsrep_local_index=0 state. So customer wants to understand why wsrep_local_index=0 node does not cause any stuck if it's server stopped. |
| Comments |
| Comment by JF D [ 2020-06-29 ] |
|
I reproduced this issue on a 3-nodes cluster running MariaDB 10.3.23 and Galera 3.29. I executed the script (deadlock.sh) on the node with wsrep_local_index=0 (master node). However when running the script on another node where wsrep_local_index is not 0 (slave) the cluster deadlock did not occur. |
| Comment by Jan Lindström (Inactive) [ 2020-10-27 ] |
|
MariaDB 10.4 and later version are not affected. |