[MDEV-19041] mysqldump can't save master position without stopping the slave during the entire dump Created: 2019-03-25  Updated: 2019-03-25

Status: Open
Project: MariaDB Server
Component/s: Backup, Replication
Affects Version/s: 10.1.38
Fix Version/s: 10.1

Type: Bug Priority: Minor
Reporter: Rick Pizzi Assignee: Andrei Elkin
Resolution: Unresolved Votes: 1
Labels: None


 Description   

Goal: take a mysqldump of a running server with it's master's coordinates saved in the dump in order to be able to use the dump to rebuild a slave. Do this without stopping the slave.

Problem: there is an option --dump-slave=2, but to my dismay this will stop the SQL slave thread the entire time. Why is this needed? And, furthermore - with such option, if you kill (gracefully. kill -15) the mysqldump process, the slave is left in the stopped state...

Please, make it possible to take a dump of a running slave with master's coordinates, without having to stop it.

Command used:

mysqldump --single-transaction --routines --triggers --dump-slave=2 -A .....


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