[MXS-2542] Add rebuild server to MariaDB Monitor Created: 2019-06-04 Updated: 2023-05-08 Resolved: 2022-07-22 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | mariadbmon |
| Affects Version/s: | None |
| Fix Version/s: | 22.08.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Todd Stoffel (Inactive) | Assignee: | Esa Korhonen |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | Rebuild, Slave | ||
| Issue Links: |
|
||||||||||||||||||||
| Sprint: | MXS-SPRINT-144, MXS-SPRINT-157, MXS-SPRINT-158, MXS-SPRINT-159, MXS-SPRINT-160, MXS-SPRINT-162 | ||||||||||||||||||||
| Description |
|
It would be nice to add a feature to MaxScale that could rebuild a corrupted machine or automatically build a new replica. That replica should then automatically join an existing cluster. This could be accomplished in a similar method that is used with Galera SST. On the current master: 1. Launch MariaBackup On the joining node: 1. Receive the socat stream |
| Comments |
| Comment by markus makela [ 2019-06-18 ] |
|
Might be a nice feature to integrate into the server as a new replication command. A sort of a dump thread could send fake replicated events until a known GTID position is reached. When the position is reached, normal replication would start. You'd essentially cause the whole database to be replicated to a slave via the replication protocol. Looks like |
| Comment by Geoff Montee (Inactive) [ 2019-11-20 ] |
|
If MDEV-21106 were implemented in MariaDB Server, then MaxScale could use the clone plugin for this. |
| Comment by Max Mether [ 2022-04-21 ] |
|
I assume this ticket is for a generic solution, not for SkySQL only? I am also worried about how exactly SkySQL clones servers, there has been issues with that process in the past. In any case, this feature is requested by a large amount of users and customers and having it in MaxScale is a great compelling solution. |