Improve --no-lock description in docs
Bug #878457 reported by
Alexey Kopytov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Reporting a part of https:/
I think here you should add a sentence that hints to using --safe-
"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.
"
Related branches
lp:~hrvojem/percona-xtrabackup/docfix
- Alexey Kopytov (community): Approve
-
Diff: 452 lines (+163/-94)8 files modifieddoc/source/conf.py (+3/-1)
doc/source/glossary.rst (+4/-4)
doc/source/howtos/recipes_ibkx_inc.rst (+1/-1)
doc/source/howtos/setting_up_replication.rst (+150/-85)
doc/source/howtos/ssh_server.rst (+1/-1)
doc/source/innobackupex/innobackupex_option_reference.rst (+2/-1)
doc/source/innobackupex/preparing_a_backup_ibk.rst (+1/-1)
doc/source/xtrabackup_bin/preparing_the_backup.rst (+1/-0)
Changed in percona-xtrabackup: | |
status: | New → Confirmed |
tags: | added: doc |
Changed in percona-xtrabackup: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXB-1137