holland-coredev team mailing list archive

[Andrew Garner <671966@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

To avoid delaying queuing the master logs, in case of a crash during a
backup, it would be nice if holland-mysqldump would run STOP SLAVE
SQL_THREAD rather than simply STOP SLAVE (which also stops the
IO_THREAD) when stop-slave is requested (a hack used to get a consistent
show slave status output, since a stock mysqldump currently has only
--master-data, but no --slave-data option).

** Affects: holland-backup
     Importance: Undecided
         Status: New

-- 
mysqldump stop-slave should only stop sql_thread
https://bugs.launchpad.net/bugs/671966
You received this bug notification because you are a member of Holland
Developers, which is the registrant for holland-backup.

Status in Holland Backup Framework: New

Bug description:
To avoid delaying queuing the master logs, in case of a crash during a backup, it would be nice if holland-mysqldump would run STOP SLAVE SQL_THREAD rather than simply STOP SLAVE (which also stops the IO_THREAD) when stop-slave is requested (a hack used to get a consistent show slave status output, since a stock mysqldump currently has only --master-data, but no --slave-data option).