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

The primary can be put in maintenance or drained with --force

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 26.10.0
    • Core
    • None
    • MXS-SPRINT-270
    • Hide
      Servers can now be set to maintenance and drain modes even if they're labeled as
      `Write` by the monitor if the `--force` flag is used.
      Show
      Servers can now be set to maintenance and drain modes even if they're labeled as `Write` by the monitor if the `--force` flag is used.

    Description

      MXS-2321 and MXS-3532 changed Maxscale to prevent setting a server into maintenance or drain modes if it's labeled as Master by the monitor. There are cases where this would be the simplest and most convenient method of blocking new connections and/or writes to the Master server. This can be changed so that the --force option in MaxCtrl also allows a server to be set into maintenance mode even if the monitor would not normally allow it.


      Original title and description: Rename and expose SERVER_DEMOTING server status

      MXS-5555 added the SERVER_DEMOTING status bit which is used to block new transactions. It should be exposed as a settable status and it could be renamed to something like SERVER_READ_ONLY if "demoting" is not good enough.

      Unlike the maintenance and drain bits, this must be allowed to be set on all servers as it would be used to prevent writes before a manual shutdown of the server. This way it would be possible to implement a "manual Galera switchover" by setting the Galera node in MaxScale into the new read-only mode and after all transactions have drained, the node could be shut down.

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 1d Original Estimate - 1d
                  1d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 2d
                  2d

                  Git Integration

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