[MDEV-7611] [PATCH] mysqldump --dump-slave always starts stopped slave Created: 2015-02-20  Updated: 2022-09-08

Status: Open
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 5.5, 10.0
Fix Version/s: 5.5

Type: Bug Priority: Minor
Reporter: Max Samoilenko Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 1
Labels: upstream, verified

Attachments: Text File mysqldump.patch    

 Description   

When making a dump with --dump-slave option, upon completion mysqldump starts slave threads even if they were not stopped by mysqldump itself. This behavior breaks delayed/manually synchronized slaves which have not to be running all the time. Please consider implementing additional check(s) for that, like in the attached patch.

P.S. The comment /* if SLAVE SQL is not running, we don't start it */ in do_start_slave_sql() is opposite and misleading.



 Comments   
Comment by Elena Stepanova [ 2015-02-20 ]

smax,

Thanks for the report and the patch.

serg,

Technically it's an upstream bug, but it's been in 'verified' for 3 years with no progress, maybe it makes sense not to wait and just to apply the patch?

Generated at Thu Feb 08 07:20:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.