[MDEV-5624] mysqldump --dump-slave option does not restart the replication if the dump has failed Created: 2014-02-06 Updated: 2014-02-21 Resolved: 2014-02-21 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.35 |
| Fix Version/s: | 5.5.36 |
| Type: | Bug | Priority: | Major |
| Reporter: | Jean Weisbuch | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | mysqldump | ||
| Environment: |
Debian Wheezy amd64 |
||
| Description |
|
Using the --dump-slave option of mysqldump stops the replication at the beginning of the dump and restarts it once its done but if the dump fails for any reason (if the database does not exists or the user doesnt have enough permission on it for example), the replication is not restarted at the end of the process. To reproduce, use a user with the REPLICATION SLAVE grant (and check that the replication is running prior) :
The slave replication is now stopped (Slave_SQL_Running = No). ps: i havent tested if a similar issue exists with --master-data. |