holland-coredev team mailing list archive

[Andrew Garner <766681@xxxxxxxxxxxxxxxxxx>]

This has been open a while and I am going to reject this right now.   I
don't want holland to get into the business of modifying mysqldump
output directly.

** Changed in: holland-backup
       Status: New => Won't Fix

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

Title:
  Start slave IO_THREAD in mysqldump output

Status in Holland Backup Framework:
  Won't Fix

Bug description:
  To immediately start queuing the master logs during a slave
  initialization from a master-data dump, it would be nice to optionally
  inject START SLAVE IO_THREAD after the CHANGE MASTER TO
  MASTER_LOG_FILE ...

  This would presumably fail if the slave had not first had CHANGE
  MASTER TO MASTER_HOST, MASTER_USER, MASTER_PASSWORD but perhaps that
  is a feature since you then avoid having to manually extract the
  CHANGE from the dump file and worse forget to do so starting at the
  master's first available.

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