holland-mysqldump in latest 1.0.5+ will only stop the sql_thread before
a mysqldump backup and only when the stop-slave option is requested.
** Changed in: holland-backup
Status: New => Fix Committed
** Changed in: holland-backup
Importance: Undecided => High
** Changed in: holland-backup
Assignee: (unassigned) => Andrew Garner (muzazzi)
** Changed in: holland-backup
Milestone: None => 1.0.6
--
You received this bug notification because you are a member of Holland
Discuss, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/671966
Title:
mysqldump stop-slave should only stop sql_thread
Status in Holland Backup Framework:
Fix Committed
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).
_______________________________________________
Mailing list: https://launchpad.net/~holland-coredev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~holland-coredev
More help : https://help.launchpad.net/ListHelp
