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

During Failover Passive MaxScale route writes to the Old Master

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Not a Bug
    • None
    • 6.4.16
    • mariadbmon
    • None
    • MXS-SPRINT-205, MXS-SPRINT-206, MXS-SPRINT-207

    Description

      In an Active/Passive MaxScale setup, a failover process can occur. During this process, the old master may come back online and be identified by the Passive MaxScale as the Master. In this event, writes may be routed to the old master. However, if the failover process completes in the Active MaxScale and the old master tries to rejoin the cluster as a slave, replication fails. This is because there could be writes routed by Passive MaxScale that occurred in the old master during the failover process.

      Attachments

        Issue Links

          Activity

            People

              esa.korhonen Esa Korhonen
              pandi.gurusamy Pandikrishnan Gurusamy
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.