[MDEV-19248] Implement MASTER_BIND for CHANGE MASTER Created: 2019-04-13  Updated: 2023-11-30

Status: Open
Project: MariaDB Server
Component/s: Admin statements, Replication
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: Papercut, beginner-friendly, compat56

Issue Links:
PartOf
is part of MDEV-28906 MySQL 8.0 desired compatibility Open
Relates
relates to MDEV-21465 Add --bind-address parameter for outg... Stalled

 Description   

MySQL has allowed the MASTER_BIND option for CHANGE MASTER since MySQL 5.6.2:

MASTER_BIND is for use on replication slaves having multiple network interfaces, and determines which of the slave's network interfaces is chosen for connecting to the master.

The address configured with this option, if any, can be seen in the Master_Bind column of the output from SHOW SLAVE STATUS. If you are using slave status log tables (server started with --master-info-repository=TABLE), the value can also be seen as the Master_bind column of the mysql.slave_master_info table.

The ability to bind a replication slave to a specific network interface was added in MySQL 5.6.2. This is also supported by MySQL NDB Cluster 7.3.1 and later.

https://dev.mysql.com/doc/refman/5.6/en/change-master-to.html

Do we want to implement this option?

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


Generated at Thu Feb 08 08:50:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.