holland-coredev team mailing list archive

[m00dawg <tim@xxxxxxxxxxxxxxxxxxxxx>]

Resolved in master. Sorry, I meant to do that on my own branch but was
failing with GIT. The documentation now reads:

###
Stops the SQL_THREAD during the backup. This means that writes
from the master will continue to spool but will not be replayed.
This helps avoid lock wait timeouts among things while still
allowing data to be spooled from the master.

Note that previous versions of Holland prior to 1.0.6 simply
ran a STOP SLAVE instead, which suspends both replicaiton
threads.
###

-- 
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/810561

Title:
  mysqldump stop-slave documentation is out of date

Status in Holland Backup Framework:
  New

Bug description:
  Currently the stop-slave documentation here:

  http://docs.hollandbackup.org/provider_configs/mysqldump.html

  Still states:

  "...Suspending the slave does not change the backups, but does prevent
  the slave from spooling up relay logs. The default is not to suspend
  the slave (if applicable)."

  However, this was addressed in v1.0.6 as noted in CHANGES.txt:

  holland-mysqldump
  +++++++++++++++++
  - holland-mysqldump now only stops the SQL_THREAD when stop-slave is 
    requested

  So this is a minor documentation bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/holland-backup/+bug/810561/+subscriptions