holland-coredev team mailing list archive

[MikeG <766681@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

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

-- 
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:
  New

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.