[MXS-4917] Master to be put Read-Only when Disk full via MaxScale Created: 2024-01-03 Updated: 2024-02-06 |
|
| Status: | Open |
| Project: | MariaDB MaxScale |
| Component/s: | failover |
| Affects Version/s: | 23.08.4 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Michael Malgeri (Inactive) | Assignee: | Joe Cotellese |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Maxscale software platform |
||
| Description |
|
Description: Customer currently has MaxScale in primary replica configuration. When disk fills to 100% on Primary there can be corruption. Customer already has Critical alerts when disk reaches 95% full. Customer would like to have Primary change to Read-Only when this threshold is reached. Currently, maxscale supports switchover on disk full (and maintenance on disk full for replicas), but Customer would like to leave the cluster in-tact and support Read-only transaction mode on Master node and continue to detect node failures (replicas) while in this state. Customer admin attempted to put Primary into read_only mode, however maxscale recognizes this and changes it back. Also, locking tables for read only will not work for the customer since it hangs all other connections. Summary: request for feature enhancement to add a "read_only_on_disk_full" option for Maxscale similar to switchover_on_disk_full? |