[MDEV-30998] Unexpected server stop Created: 2023-04-04 Updated: 2023-06-27 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.6 |
| Fix Version/s: | 10.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | COUNOTTE CEDRIC | Assignee: | Seppo Jaakola |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
This is the last message received on one of the server in a 3-server cluster. 2023-04-04 10:19:40 0 [Warning] WSREP: unserialize error invalid protocol version 2: 71 (Protocol error) Other nodes remained synched, I could restart this node with a simple sudo systemctl start mariadb. |
| Comments |
| Comment by Sergei Golubchik [ 2023-05-22 ] | |
|
What MariaDB version? How can we repeat this issue? | |
| Comment by COUNOTTE CEDRIC [ 2023-05-23 ] | |
|
Version is 10.6.x (x upto 12). I believe that crash was related to this bug report: I've configured the mentioned workaround and had no crash so far:
Now I've upgraded one of our cluster to 10.6.13 and each time I restart a node being a replication slave of the other cluster, it keeps crashing until I restart the whole cluster which causes a SST re-sync of the 2 other nodes of the cluster. Too busy to open a bug report atm. |