Bug #79019 mysqldump starts slave with --dump-slave option even it had been stopped before
Submitted: 29 Oct 2015 13:15 Modified: 16 May 2019 8:58
Reporter: Timur Solodovnikov Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:5.6.21 OS:CentOS (5.X)
Assigned to: CPU Architecture:Any
Tags: MySQL, mysqldump, slave

[29 Oct 2015 13:15] Timur Solodovnikov
Description:
mysqldump starts slave with --dump-slave option even it had been stopped before dump.

This is not documented behaviour, I had some problems with it.

How to repeat:
stop slave;
mysql dump some DB with --sump-slave option.

Once dump is finished, you can see a run slave.

Suggested fix:
Don't start slave if it was stopped.
[15 May 2019 23:06] MySQL Verification Team
Hi,

This is how it worked for a while and I doubt we can just "not start slave" in that case. I did change this report to "Feature request" so we can add a explicit "--do-not-start-slave" there.

thanks for your report
Bogdan