Start slave IO_THREAD in mysqldump output
Bug #766681 reported by
MikeG
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
holland-backup |
Won't Fix
|
Undecided
|
Unassigned |
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 post a comment you must log in.
It sounds like a good idea - I'm just trying to think of some of the edge cases. So far the worst case I can think of is queueing logs one might not use (such as when doing point-in- time-recovery) . I think this should be a feature that must be enabled (ie not default) so at least people that turn it on should have an idea of what they are getting into?