--slave-info --no-lock --safe-slave-backup --rsync
Registered by
Ryan Huddleston
For come users it's not possible to run "FLUSH TABLES WITH READ LOCK" even on a slave server. To avoid this another option is to use --slave-info --no-lock --safe-slave-backup when only using InnoDB tables. For customers with thousands of tables the time taken just to backup the frm files can stop replication for an unacceptable duration. To improve this situation the --rsync option should rsync the frm files once prior to stopping replication
Blueprint information
- Status:
- Complete
- Approver:
- Alexey Kopytov
- Priority:
- High
- Drafter:
- Alexey Kopytov
- Direction:
- Approved
- Assignee:
- Alexey Kopytov
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Alexey Kopytov
Related branches
Sprints
Whiteboard
This is essentially a duplicate of bug #1182726. With the fix for that bug, --slave-info --no-lock --safe-slave-backup will only stop the SQL thread for a short period of time to get the slave info _after_ MyISAM/frm files have been copied.
(?)
