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

Support DO_DOMAIN_IDS and IGNORE_DOMAIN_IDS for the Binlog Router

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Do
    • 2.3.8
    • N/A
    • binlogrouter
    • None

    Description

      It looks like the Binlog Router does not currently support the DO_DOMAIN_IDS and IGNORE_DOMAIN_IDS options for CHANGE MASTER:

      https://github.com/mariadb-corporation/MaxScale/blob/maxscale-2.3.8/server/modules/routing/binlogrouter/blr_slave.cc#L5318

      These options would be especially useful when using Binlog Router with Galera Cluster and secondary masters. See MXS-2580 for more information.

      The options are described here:

      https://mariadb.com/kb/en/library/change-master-to/#do_domain_ids

      https://mariadb.com/kb/en/library/change-master-to/#ignore_domain_ids

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MXS-2580 Clarify requirements of binlog router secondary masters

          • Major - Major loss of function.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-4989 Support for GTID in mysqlbinlog

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-20119 Implement the --do-domain-ids, --ignore-domain-ids, and --ignore-server-ids options for mysqlbinlog

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-22905 Support DO_DOMAIN_IDS and IGNORE_DOMAIN_IDS in replication handshake

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MXS-2589 Adapt binlog router to

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Descending order - Click to sort in ascending order
            GeoffMontee Geoff Montee (Inactive) added a comment -

            This is already available using segments with Galera natively.

            Galera's segments are not related this feature request, and Galera's segments can not be used to implement what this feature request is asking for.

            Galera replication should handle this scenario. This is not possible with binlog router.

            Galera's replication can not handle this scenario. The whole point of this feature request is that each Galera Cluster node has two GTID domains: one for WSREP transactions, and one for non-WSREP transactions. This means that if you try to use Galera with Binlog Router, and if you try to use the router's secondary master feature to provide seamless failover for the Binlog Router, then this failover process has a high likelihood of failing if any non-WSREP transactions has been executed on the secondary master. This feature request is asking for a specific solution: Binlog Router could support DO_DOMAIN_ID/IGNORE_DOMAIN_ID, just like MariaDB Server does, so that the Binlog Router can be configured to only replicate the domain of the WSREP transactions.

            However, regardless of this feature request for the Binlog Router, DO_DOMAIN_ID/IGNORE_DOMAIN_ID are only partially functional in MariaDB Server at the moment. See the conversation in MDEV-20438 about some ideas on how these options may be improved in the future.

            It seems as though this feature request may have been closed without having a good understanding of what it is asking for. If you have any questions about it, please let me know.

            GeoffMontee Geoff Montee (Inactive) added a comment - This is already available using segments with Galera natively. Galera's segments are not related this feature request, and Galera's segments can not be used to implement what this feature request is asking for. Galera replication should handle this scenario. This is not possible with binlog router. Galera's replication can not handle this scenario. The whole point of this feature request is that each Galera Cluster node has two GTID domains: one for WSREP transactions, and one for non-WSREP transactions. This means that if you try to use Galera with Binlog Router, and if you try to use the router's secondary master feature to provide seamless failover for the Binlog Router, then this failover process has a high likelihood of failing if any non-WSREP transactions has been executed on the secondary master. This feature request is asking for a specific solution: Binlog Router could support DO_DOMAIN_ID/IGNORE_DOMAIN_ID, just like MariaDB Server does, so that the Binlog Router can be configured to only replicate the domain of the WSREP transactions. However, regardless of this feature request for the Binlog Router, DO_DOMAIN_ID/IGNORE_DOMAIN_ID are only partially functional in MariaDB Server at the moment. See the conversation in MDEV-20438 about some ideas on how these options may be improved in the future. It seems as though this feature request may have been closed without having a good understanding of what it is asking for. If you have any questions about it, please let me know.
            toddstoffel Todd Stoffel (Inactive) added a comment -

            Galera replication should handle this scenario. This is not possible with binlog router.

            toddstoffel Todd Stoffel (Inactive) added a comment - Galera replication should handle this scenario. This is not possible with binlog router.
            Richard Richard Stracke added a comment -

            toddstoffel

            segments on galera has only an effect for communicating between galera nodes.

            The segment information will wether not saved in the binlog nor it can be used to separate transactions which will not part of a writeset (only binlog) from cluster transactions, which is needed for this usecase.

            Richard Richard Stracke added a comment - toddstoffel segments on galera has only an effect for communicating between galera nodes. The segment information will wether not saved in the binlog nor it can be used to separate transactions which will not part of a writeset (only binlog) from cluster transactions, which is needed for this usecase.
            toddstoffel Todd Stoffel (Inactive) added a comment -

            This is already available using segments with Galera natively.

            toddstoffel Todd Stoffel (Inactive) added a comment - This is already available using segments with Galera natively.

            People

              toddstoffel Todd Stoffel (Inactive)
              GeoffMontee Geoff Montee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.