Rename lock-wait-timeout, lock-wait-query-type, lock-wait-threshold in 2.3
Bug #1411157 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
|
Wishlist
|
Alexey Kopytov | ||
2.3 |
Fix Released
|
Wishlist
|
Alexey Kopytov |
Bug Description
The lock-wait-timeout innobackupex option is quite confusing because there's a server variable with the same name and different semantics.
We should rename it (and other lock-wait-* variables in PXB for consistency) to something different. For example, use ftwrl- prefix instead of lock-, since the feature only applies to FTWRL anyway.
Related branches
lp:~akopytov/percona-xtrabackup/bug1411157
- Alexey Kopytov (community): Approve
-
Diff: 211 lines (+47/-47)4 files modifiedstorage/innobase/xtrabackup/doc/source/innobackupex/improved_ftwrl.rst (+11/-11)
storage/innobase/xtrabackup/doc/source/innobackupex/innobackupex_option_reference.rst (+6/-6)
storage/innobase/xtrabackup/innobackupex.pl (+21/-21)
storage/innobase/xtrabackup/test/t/kill_long_selects.sh (+9/-9)
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-1012