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

Galera Monitor keeps replication from an external cluster working when its primary changes

    XMLWordPrintable

Details

    • MXS-SPRINT-277, MXS-SPRINT-278, MXS-SPRINT-279, MXS-SPRINT-280
    • Hide
      Galera Monitor supports external replication management by relying on the
      results of another monitor. This allows the monitor to update the external
      replication connection if the external primary goes down or its role changes.
      See
      [Galera Monitor documentation]({maxscale}/reference/maxscale-monitors/galera-monitor#external-replication-management)
      for more information.
      Show
      Galera Monitor supports external replication management by relying on the results of another monitor. This allows the monitor to update the external replication connection if the external primary goes down or its role changes. See [Galera Monitor documentation]({maxscale}/reference/maxscale-monitors/galera-monitor#external-replication-management) for more information.

    Description

      Add external_replication_monitor and external_replication_primary_role to GaleraMon.

      Original description:
      Since original GTID will be forwarded to all nodes (MDEV-20720),
      such feature should be possible.

      Given a setup like
      https://mariadb.com/kb/en/configuring-mariadb-replication-between-two-mariadb-galera-clusters/

      Also this setup with additional async replciation between the nodes.

      A workaround is to establish a maxscale readconnrouter between both galera cluster,
      with router_options=master, but this will only affect an outage of the master node, not slave node.

      So feature request here is a mechanism, that Maxscale check async replication between both galera cluster and switch slave and master node in case of a failure
      and take into account, that binlog position can be different and can determine the correct GTID.

      Attachments

        Issue Links

          Activity

            People

              esa.korhonen Esa Korhonen
              Richard Richard Stracke
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 10d Original Estimate - 10d
                  10d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 13d
                  13d

                  Git Integration

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