xtrabackup_pid remains existed after execution
Bug #1114955 reported by
Ren Xiaolei
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Low
|
Alexey Kopytov | ||
| 2.0 |
Fix Released
|
Low
|
Alexey Kopytov | ||
| 2.1 |
Fix Released
|
Low
|
Alexey Kopytov | ||
Bug Description
after executing innobackup --stream , xtrabackup_pid remains existed in the --tmpdir . Normally it should be deleted after execution.
# rpm -qi percona-xtrabackup
Name : percona-xtrabackup Relocations: (not relocatable)
Version : 2.0.5 Vendor: (none)
Release : 499.rhel5 Build Date: 2013年01月18日 星期五 04时29分13秒
Install Date: 2013年01月28日 星期一 13时44分29秒 Build Host: localhost.
Group : Server/Databases Source RPM: percona-
Size : 11344684 License: GPLv2
Signature : DSA/SHA1, 2013年01月18日 星期五 08时13分26秒, Key ID 1c4cbdcdcd2efd2a
Related branches
lp://staging/~akopytov/percona-xtrabackup/bug1114955-2.0
- Laurynas Biveinis (community): Approve
- Registry Administrators: Pending requested
-
Diff: 10 lines (+1/-0)1 file modifiedinnobackupex (+1/-0)
lp://staging/~akopytov/percona-xtrabackup/bug1114955-2.1
- Laurynas Biveinis (community): Approve
- Registry Administrators: Pending requested
-
Diff: 10 lines (+1/-0)1 file modifiedinnobackupex (+1/-0)
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #1 |
Revision history for this message
| Ren Xiaolei (julyclyde) wrote | #2 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
Confirmed as a regression introduced by the fix for #1055989. I don't see any serious issues with it though, as stale xtrabackup_pid will just be overwritten on next innobackupex invokation?