[MDEV-22307] safe_to_bootstrap is reset to 0 immediately after starting SST Created: 2020-04-19 Updated: 2021-12-23 Resolved: 2021-12-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Galera SST |
| Affects Version/s: | 10.4.12 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Adam Purkrt | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | galera | ||
| Environment: |
gentoo linux |
||
| Description |
|
A galera cluster of three nodes (g1, g2, g3). g2 and g3 has been shut down. g1 (the first node) has been running standalone for some time. It has "safe_to_bootstrap: 1" in /var/lib/mysql/grastate.dat, and this is perfectly fine. Now if g2 (the second node) is started, after being off for prolonged time, it will start SST from g1. That, in itself, is ok. The problem is: immediately, as soon as the SST starts, the "safe_to_bootstrap:" on g1 (the donor) will change to "0". And I think it should not. If there occurs some error during SST, g1 is still the one node to bootstrap cluster from (as g2 does not contain full data yet). So the "safe_to_bootstrap:" should remain "1" on the standalone donor (g1) until the joiner (g2) is primary/synced. Only then should it be changed to "0" (and be "0" on both nodes, as long as both are running). |
| Comments |
| Comment by Jan Lindström (Inactive) [ 2021-12-23 ] |
|
This is intended behaviour. |