[MDEV-32827] grastate.dat is not updated on node shutdown. Created: 2023-11-17 Updated: 2023-12-15 Resolved: 2023-12-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Galera SST |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Blocker |
| Reporter: | MikaH | Assignee: | Julius Goryavsky |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
CentOS Linux release 7.7.1908. 3 nodes. Intel(R) Xeon(R) Gold 6142 CPU @ 2.60GHz with 64 CPU's. Bare metal. 512GB RAM, galera-enterprise-4-26.4.14-1.el7_9.src.rpm |
||
| Attachments: |
|
| Description |
|
During the normal shutdown of MariaDB 10.5.22 cluster node, grastate.dat-file is not updated and that leads to SST on start always. IST won't be available.
|
| Comments |
| Comment by Rick Pizzi [ 2023-11-17 ] |
|
The cluster has not been bootstrapped correctly and has a null cluster UUID (all zeros). |
| Comment by MikaH [ 2023-11-17 ] |
|
Okay. Someone has bootstrapped the cluster before I was involved to this. What would be the best way to Bootstrap the cluster and avoiding SST's? Would this work: |
| Comment by Rick Pizzi [ 2023-11-17 ] |
|
You should never copy the state file to other nodes. |
| Comment by MikaH [ 2023-11-17 ] |
|
Well, that kinda sucks. SST took 8h18min to complete. With little trick it is possible to shrink to few minutes. |
| Comment by Rick Pizzi [ 2023-11-17 ] |
|
Also you cannot avoid SST if you don't have a valid state for a node. |
| Comment by Rick Pizzi [ 2023-11-17 ] |
|
The "trick" implies to have a valid state on a node, you do not have it. |
| Comment by MikaH [ 2023-11-17 ] |
|
Yeah, automatic SST is the easiest way but having dataset size like 7TB not a good one. You have documented Manual SST here: https://mariadb.com/kb/en/manual-sst-of-galera-cluster-node-with-mariabackup/ The tricky part with that Manual SST is the file grastate.dat, single typo, extra empty line, leads to SST instead of IST. Let's close this ticket and if the issue re-appears after cluster bootstrapped again, I'll return here. If nothing Is heard, all is ok |
| Comment by Julius Goryavsky [ 2023-12-15 ] |
|
I am closing this ticket because according to available information it is not a bug, if the problem appears after correct bootstrap we will reopen this ticket. |