[MXS-4743] switchover-force should ignore replication delay Created: 2023-09-05 Updated: 2023-11-15 Resolved: 2023-10-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | mariadbmon |
| Affects Version/s: | 2.5, 6.4.10, 22.08.8, 23.08.0 |
| Fix Version/s: | 23.08.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Massimo | Assignee: | Esa Korhonen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Hi on a topology of a PRIMARY/REPLICAS,where replica are bihind the master, customer want to promote a slave that is behind and have it has a primary.
just promote that server as primary now. In this scenario, HA is more important of the data, and the customer is aware of it, but it want to control with a command call directly on maxscale and not really do other tricks on dbs servers or call reset call replication. call command mariadbmon switchover MyMonitor NewPrimaryServ --destroy it sound like a perfect call command |
| Comments |
| Comment by Massimo [ 2023-09-21 ] |
|
esa.korhonen this is expected, even replication broken eventually. As i describe, they want to have HA over the data consistency and/or dataloss . So maxscale, promote this as master, nomatter what. |