[MDEV-15610] Add SST for asynchronous slaves Created: 2018-03-20  Updated: 2022-08-26  Resolved: 2022-08-26

Status: Closed
Project: MariaDB Server
Component/s: N/A
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Manjot Singh (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 2
Labels: sst

Issue Links:
Relates
relates to MDEV-7502 Automatic provisioning of slave Open
relates to MDEV-21106 Port clone plugin from MySQL Open
relates to MXS-2542 Add rebuild server to MariaDB Monitor Closed

 Description   

One of the common pain points for DBAs is creating and managing slaves. Since MariaDB already contains Galera libraries, the SST portion could be leveraged to allow async slave creation after a fresh install.

Flow:

  1. New server is provisioned
  2. MariaDB Installed
  3. Server is brought up
  4. root user issues CHANGE MASTER TO ...... MASTER_SST=1;
  5. Server initiates SST utilizing replication user/pass
  6. After server comes back up, it connects as an asynchronous or semi-sync slave

 Comments   
Comment by Daniel Black [ 2018-03-23 ]

would require:

  • donor sst scripts to provide replication file/offset or gtid position at the point of the snapshot (MDEV-5968)
  • joiner side of the scripts would need know the connection name (of the CHANGE MASTER ['connection name'] TO)
Comment by Manjot Singh (Inactive) [ 2018-03-23 ]
  • Donor scripts could easily provide this as they use xtrabackup or mariadb-backup which can provide xtrabackup_binlog_info (MDEV-5968 is unrelated as that relates to mysqldump which SST does not use)
  • I think to start, this idea cannot be used with MSR (feature could be worked on later)
Comment by Geoff Montee (Inactive) [ 2019-11-20 ]

Galera's SST scripts are very fragile, and when they break, the issues can be difficult to debug. If MDEV-21106 were implemented in MariaDB Server, then the clone plugin could also be used for this.

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