Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4917

Master to be put Read-Only when Disk full via MaxScale

    XMLWordPrintable

Details

    • New Feature
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 23.08.4
    • None
    • failover
    • None
    • 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?

      Attachments

        Activity

          People

            JoeCotellese Joe Cotellese
            mmalgeri Michael Malgeri (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.