Details
-
New Feature
-
Status: Stalled (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
-
Q2/2025 Development, Q3/2025 Server Development
Description
When having multiple replication channels (or when changing what primary to replicate from often) and using two-way TLS the client certificate and CA files used as MASTER_SSL_* parameters in CHANGE MASTER TO will usually be the same and not change between connections to different primaries.
So it may make sense to be able to configure a client certificate to be used for all replication channels in a central place instead of having to add MASTER_SSL_CA, MASTER_SSL_CERT and MASTER_SSL_KEY (and maybe MASTER_SSL_VERIFY_SERVER_CERT, too) again and again each time a CHANGE MASTER TO is done.
E.g.:
replication_ssl_ca=...
|
replication_ssl_cert=...
|
replication_ssl_key=...
|
and maybe also an explicit MASTER_SSL_USE_DEFAULTS option to CHANGE MASTER to only use such default settings on demand.
Attachments
Issue Links
- includes
-
MDEV-37362 Save the set/unset state of CHANGE MASTER configurations
-
- Stalled
-
- relates to
-
MDEV-35584 11.4 relpica can't replicate form 10.6 master not configured for SSL using CHANGE MASTER default settings
-
- Open
-
-
MDEV-37530 Refactor Master & Relay Log info to iterable tuples
-
- Open
-
-
MDEV-36141 Master & Relay Log Info: expand init_intvar_from_file from atoi to atoll
-
- Open
-
-
MXS-4096 Binlog Routers SHOW SLAVE STATUS does not show SSL information
-
- Closed
-
- split to
-
MDEV-36841 No ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MAX warning when setting @@GLOBAL.slave_net_timeout to below CHANGE MASTER’s master_heartbeat_period
-
- Open
-