kill_long_selects still unstable
Bug #1326224 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
|
Low
|
Sergei Glushchenko | ||
| 2.1 |
Fix Released
|
Low
|
Sergei Glushchenko | ||
| 2.2 |
Fix Released
|
Low
|
Sergei Glushchenko | ||
Bug Description
The kill_long_
It seems to be specific to CentOS 5 slaves.
Related branches
lp:~sergei.glushchenko/percona-xtrabackup/2.2-xb-bug1326224
- Alexey Kopytov (community): Approve
-
Diff: 92 lines (+23/-15)1 file modifiedstorage/innobase/xtrabackup/test/t/kill_long_selects.sh (+23/-15)
lp:~sergei.glushchenko/percona-xtrabackup/2.1-xb-bug1326224
- Alexey Kopytov (community): Approve
-
Diff: 86 lines (+21/-13)1 file modifiedtest/t/kill_long_selects.sh (+21/-13)
- Percona core: Pending requested
-
Diff: 85 lines (+20/-13)1 file modifiedstorage/innobase/xtrabackup/test/t/kill_long_selects.sh (+20/-13)
Revision history for this message
| Sergei Glushchenko (sergei.glushchenko) wrote | #1 |
Revision history for this message
| Sergei Glushchenko (sergei.glushchenko) wrote | #2 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
Related code
bg_run bg_select_pid "mysql_select 200"
bg_run bg_update_pid "sleep 1" "mysql_update 5"
innobackupex $topdir/full --kill-
bg_wait_fail $bg_select_pid
bg_wait_ok $bg_update_pid
select apparently started after innobackupex proceeded with backup, so it was not killed as expected.
All failures happened at the same place.
I'll fix it by inserting delay after
bg_run bg_select_pid "mysql_select 200"