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

Support the server priority-setting in MariaDB Monitor

    XMLWordPrintable

Details

    • New Feature
    • Status: In Progress (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • 27.10.0
    • mariadbmon
    • None

    Description

      Current status:
      As of 27.10.0, MariaDB Monitor will respect the server "priority" setting when autoselecting a server for promotion during failover/switchover. The monitor will also consider the priority when selecting a primary during startup, if necessary. This second case only applies if the topology is ambiguous, i.e. it is not clear which server is the replication primary.

      Original description:
      When multiple replicas are equally up to date and suitable for promotion, there is no configurable mechanism for mariadbmon to select the best promotion replica to express a preference among them.

      This enhancement proposes extending mariadbmon to support priority-based replica selection by utilizing the existing priority server attribute, similar to how it is used by galeramon.

      This would provide greater flexibility for asynchronous replication deployments without altering the current failover logic for determining eligible promotion candidates.

      The idea is to extend MaxScale to include this functionality, following the same logic of negative value means DO NOT USE the server, and lowest value has a higher preference. This provides the user with a more flexible approach in selecting up to date replicas. In practice MaxScale will most likely not trigger a failover in sub-second timescales so by then multiple replicas may be in the same state replicating from the now dead master. Optionally adding this final check if use_priority=true and setting priorities to individual hosts would be a useful improvement.

      Attachments

        Issue Links

          Activity

            People

              esa.korhonen Esa Korhonen
              Koustuv Koustuv Chatterjee
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - 5d
                  5d
                  Remaining:
                  Time Spent - 4d Remaining Estimate - 1d
                  1d
                  Logged:
                  Time Spent - 4d Remaining Estimate - 1d
                  4d

                  Git Integration

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