TritonDataCenter / TritonDataCenter/pkgsrc-joyent
quickbackup-percona always locks database
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 32
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Would be great to have an option to enable --no-lock (and with it --safe-slave-backup) in backups. This is useful on busy servers where even a few seconds of read-locked tables is too much. Obviously this comes with some danger and should only be used where the binlog position is not needed (e.g. no async replication).
I ran across the need for this when running backups on a server where only system tables are MyISAM, but xtrabackup still read-locked everything for 30+ seconds, sometimes many minutes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the quickbackup-percona package entry point and trace how backup options are passed to xtrabackup. Review the requested --no-lock and --safe-slave-backup behavior, including the stated limitation around binlog positions, and verify that the new option can be used for backups on busy servers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100