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 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.
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.
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.
New Feature
Major
MXS-2580 Clarify requirements of binlog router secondary masters
This is already available using segments with Galera natively.