Race condition in start_query_killer child code can cause parent MySQL connection to close
Bug #1239728 reported by
Sergei Glushchenko
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.1 |
Fix Released
|
Medium
|
Sergei Glushchenko | ||
2.2 |
Fix Released
|
Medium
|
Sergei Glushchenko |
Bug Description
Child process do
1. Set SIGHUP handler to hadle termination request
2. Set InactiveDestroy for parent's MySQL connection
If child signaled to terminate before 1 and 2 happened, parent connection will be shut down.
This bug is forked from https:/
Related branches
lp:~sergei.glushchenko/percona-xtrabackup/2.1-xb-bug1239728
- Alexey Kopytov (community): Approve
-
Diff: 27 lines (+7/-0)1 file modifiedinnobackupex (+7/-0)
lp:~sergei.glushchenko/percona-xtrabackup/2.2-xb-bug1239728
- Alexey Kopytov (community): Approve
-
Diff: 27 lines (+7/-0)1 file modifiedxtrabackup/innobackupex (+7/-0)
Changed in percona-xtrabackup: | |
assignee: | nobody → Sergei Glushchenko (sergei.glushchenko) |
To post a comment you must log in.
AutoInactiveDestroy seems not an option. Only precise/ quantal/ raring workers seems have it.