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

Priority of Master Promotion

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.5.10
    • Component/s: failover
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-128

      Description

      In several topologies , there are servers that are more suited to be master if possible and others that might be a DR or we would only like to be a master as a last resort.

      I would like the ability to prioritize the servers that are reviewed for master eligibility in a failover.
      For example, If I am currently running master on MariaDB-1 and I also have MariaDB-2, MariaDB-3, and MariaDB-DR, In the event of failover, I want MariaDB-2 and then MariaDB-3 to be checked for Master viability before ever checking MariaDB-DR. I don't want to exclude DR entirely with servers_no_promotion, but I want it to be the very last resort in the event 1, 2, & 3 are all down.

      Similarly, I might have more resources allocated to MariaDB1 & MariaDB2 but have a smaller server running as a backup slave on MariaDB3 (not an ideal scenario, but not uncommon with limited budgets). In a failover scenario, I might want to always prioritize failing over to 1 & 2 before resorting to 3.

        Attachments

          Activity

            People

            Assignee:
            esa.korhonen Esa Korhonen
            Reporter:
            ksizemore Kathryn Sizemore
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

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