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

Fixing M/M replication between datacenters when Master changes in multi-DC environment

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Do
    • None
    • 2.3.0
    • mariadbmon
    • None
    • MXS-SPRINT-58, MXS-SPRINT-59, MXS-SPRINT-60, MXS-SPRINT-61, MXS-SPRINT-62, MXS-SPRINT-63, MXS-SPRINT-64, MXS-SPRINT-65

    Description

      Fixing M/M replication between datacenters when Master changes in either one for following configuration

      Add an automation option so that when MaxScale node on mate-DC does switchover or failover, local master's external master is re-homed to the new master in mate-DC.

      This requires either (A) communication between the two MaxScales, or alternatively (B) both MaxScales need to monitor both clusters. B seems like an easier option. Both MaxScales could have two monitors, one for the local and one for the external cluster. The local monitor module queries the external monitor for the master server regularly, or the external monitor notifies the local monitor if its master changes.

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            dshjoshi Dipti Joshi (Inactive)
            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.