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

switchover-force should ignore replication delay

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.5, 6.4.10, 22.08.8, 23.08.0
    • 23.08.2
    • mariadbmon
    • None

    Description

      Hi

      on a topology of a PRIMARY/REPLICAS,where replica are bihind the master, customer want to promote a slave that is behind and have it has a primary.

      • They dont want to wait the new primary end with the relay log
      • They dont care about the data lost

      just promote that server as primary now.

      In this scenario, HA is more important of the data, and the customer is aware of it, but it want to control with a command call directly on maxscale and not really do other tricks on dbs servers or call reset call replication.

      call command mariadbmon switchover MyMonitor NewPrimaryServ --destroy

      it sound like a perfect call command

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            massimo.disaro Massimo
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.