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

Handle multiple replication sources on rejoin

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6
    • Fix Version/s: 6.2.0
    • Component/s: mariadbmon
    • Labels:
      None

      Description

      When mariadbmon performs a failover, it currently merges all the replication connections from the old master to the newly promoted master. This poses a problem: if a rejoining server has more than one replication stream configured, the rejoin won't be attempted:

      Server 'server2' has multiple slave connections, cannot rejoin.
      

      To fully support an infinite amount of failovers, the rejoining process must clear out all existing replication streams from the server to be rejoined. As this is an irreversible process, it should only be attempted when enforce_simple_topology is enabled.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.