[MDEV-15933] Cannot resume Node SYNCED state when wsrep_desync is done after FTWRL Created: 2018-04-19 Updated: 2018-08-15 Resolved: 2018-08-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 10.1, 10.3.6, 10.2 |
| Fix Version/s: | 10.1.36, 10.2.18, 10.3.10 |
| Type: | Bug | Priority: | Major |
| Reporter: | Zdravelina Sokolovska (Inactive) | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
CentOS 7.4; Galera 2 Nodes |
||
| Issue Links: |
|
||||||||
| Description |
|
Cannot resume Node SYNCED state when wsrep_desync is done after FTWRL 1. Issue ' flush tables with read lock;' on Galera Node 2. Set wsrep_desync – Command hangs and wsrep_desync=1 is not applied , MariaDB [(none)]> set global wsrep_desync=1; ---
---
--- Node moved in DESYNCED state and cannot be recovered MariaDB [(none)]> unlock tables ; MariaDB [(none)]> show variables like '%wsrep_desync%' ;
--------------
-------------- MariaDB [(none)]> show status like 'wsrep_local_state_comment' ;
--------------------------
-------------------------- |
| Comments |
| Comment by Zdravelina Sokolovska (Inactive) [ 2018-04-19 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
In addition fail restart mariadb.service
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mario Karuza (Inactive) [ 2018-08-14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This is fixed by not allowing to set wsrep_desync after global read lock is acquired. |