[Documentation] Caveats with --no-lock should be clearly mentioned
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Hrvoje Matijakovic | ||
Bug Description
Currently it states:
"""
--no-lock
Use this option to disable table lock with FLUSH TABLES WITH READ LOCK. Use it only if ALL your tables are InnoDB and you DO NOT CARE about the binary log position of the backup. If you are considering to use --no-lock because your backups are failing to acquire the lock, this could be because of incoming replication events preventing the lock from succeeding. Please try using --safe-slave-backup to momentarily stop the replication slave thread, this may help the backup to succeed and you then don’t need to resort to using --no-lock.
"""
I think the condition of no DDL being executed should also be added, running a DDL otherwise during --no-lock + innobackupex can lead to inconsistencies. Reasons for that can also be added to explain why (DDL is non-transactional, hence ibd file creation not recorded in redo logs etc)
Related branches
- Stewart Smith (community): Approve
-
Diff: 293 lines (+54/-37)9 files modifieddoc/source/innobackupex/incremental_backups_innobackupex.rst (+9/-5)
doc/source/innobackupex/innobackupex_option_reference.rst (+3/-3)
doc/source/innobackupex/privileges.rst (+4/-1)
doc/source/installation/compiling_xtrabackup.rst (+5/-5)
doc/source/percona-theme/layout.html (+13/-15)
doc/source/percona-theme/static/percona.com.css (+3/-3)
doc/source/xtrabackup_bin/choosing_binary.rst (+7/-1)
doc/source/xtrabackup_bin/incremental_backups.rst (+5/-1)
innobackupex (+5/-3)
- Stewart Smith (community): Approve
-
Diff: 300 lines (+54/-37)9 files modifieddoc/source/innobackupex/incremental_backups_innobackupex.rst (+9/-5)
doc/source/innobackupex/innobackupex_option_reference.rst (+3/-3)
doc/source/innobackupex/privileges.rst (+4/-1)
doc/source/installation/compiling_xtrabackup.rst (+5/-5)
doc/source/percona-theme/layout.html (+13/-15)
doc/source/percona-theme/static/percona.com.css (+3/-3)
doc/source/xtrabackup_bin/choosing_binary.rst (+7/-1)
doc/source/xtrabackup_bin/incremental_backups.rst (+5/-1)
innobackupex (+5/-3)
| Alexey Kopytov (akopytov) wrote | #1 |
| Changed in percona-xtrabackup: | |
| importance: | Undecided → Medium |
| Changed in percona-xtrabackup: | |
| status: | New → In Progress |
| Changed in percona-xtrabackup: | |
| status: | In Progress → Fix Committed |
| Changed in percona-xtrabackup: | |
| status: | Fix Committed → Fix Released |
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
Not only .ibd file creation is not redo-logged, but also .frm files creation/
1. No DDL to any tables occurs during a backup.
2. No updates to any tables other than InnoDB occur during a backup (this include updates to system MyISAM tables in the 'mysql' database).