This is a request to make the time interval between checks done by log copying thread configurable
Bug #1125993 reported by
Ovais Tariq
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Sergei Glushchenko | ||
| 2.0 |
Fix Released
|
High
|
Sergei Glushchenko | ||
| 2.1 |
Fix Released
|
Medium
|
Sergei Glushchenko | ||
Bug Description
Currently the log copying thread checks the transactional logs every second to see if there were any new log records written. This is a request to make the time interval between checks configurable. Making it configurable will allow to reduce the time interval between checks which can prevent Xtrabackup failures that are caused by the log records in the transactional log being overwritten before they are copied by the log copying thread.
Related branches
lp:~sergei.glushchenko/percona-xtrabackup/2.0-bug1125993
- Alexey Kopytov (community): Approve
-
Diff: 234 lines (+85/-11)5 files modifieddoc/source/innobackupex/innobackupex_option_reference.rst (+4/-0)
doc/source/xtrabackup_bin/xbk_option_reference.rst (+4/-0)
innobackupex (+9/-0)
src/xtrabackup.cc (+53/-11)
test/t/bug1125993.sh (+15/-0)
lp:~sergei.glushchenko/percona-xtrabackup/2.1-bug1125993
- Alexey Kopytov (community): Approve
-
Diff: 244 lines (+83/-11)7 files modifieddoc/source/innobackupex/innobackupex_option_reference.rst (+4/-0)
doc/source/xtrabackup_bin/xbk_option_reference.rst (+4/-0)
innobackupex (+9/-0)
src/innodb_int.cc (+19/-0)
src/innodb_int.h (+12/-0)
src/xtrabackup.cc (+20/-11)
test/t/bug1125993.sh (+15/-0)
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/