Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Do
Description
Description of DO_DOMAIN_IDS is
"The DO_DOMAIN_IDS option for CHANGE MASTER can be used to configure a replication slave to only apply binary log events if the transaction's GTID is in a specific gtid_domain_id value"
The filter works after the replication handshake, which is counter intuitive.
It would more consisten, if the replication handshake respect DO_DOMAIN_IDS and
IGNORE_DOMAIN_IDS.
One possible usecase is, if a async slave is a slave from a galera node. slave_pos is
(, <server only gtid>)
After an SST the <server only gtid> is not anymore in the binlog, but still the <any wsrep gtid> .
This breaks replication. Repecting DO_DOMAIN_IDS in replication handshake can help here.
Attachments
Issue Links
- relates to
-
MDEV-20119 Implement the --do-domain-ids, --ignore-domain-ids, and --ignore-server-ids options for mysqlbinlog
-
- Closed
-
-
MDEV-34485 Ignored GTID domain IDs still appear in gtid_slave_pos
-
- Open
-
-
MDEV-20715 Implement system variable to disallow local GTIDs in Galera
-
- Closed
-
-
MXS-2580 Clarify requirements of binlog router secondary masters
-
- Closed
-
-
MXS-2581 Support DO_DOMAIN_IDS and IGNORE_DOMAIN_IDS for the Binlog Router
-
- Closed
-
I could see following use case for different domain_id's
node1 <--->node2<--->node3 (Galera cluster domain_id=1) node4<--->node5<--->node6 (Galera cluster domain_id=2)
| (Async replication) | (Async replication)
node7<--->node8<--->node9 (Galera cluster domain_id=3)
Here I have 2 master Galera clusters and one replica Galera cluster. Even when lets say master Galera cluster with domain_id=1 goes down and we change master, I do not see reason to ignore some events from certain domain. Note that inside a cluster domain_id must be the same as documented and currently I do not see reason to change that.
If this feature is important to customer(s), please provide more detailed description on use case and how it should work. Current description is too vague for feature request. Therefore, I can't evaluate possible consequences and/or task estimates.