xtrabackup_pid remains existed after execution

Bug #1114955 reported by Ren Xiaolei on 2013-02-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov
Fix Released
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.localdomain
Group : Server/Databases Source RPM: percona-xtrabackup-2.0.5-499.rhel5.src.rpm
Size : 11344684 License: GPLv2
Signature : DSA/SHA1, 2013年01月18日 星期五 08时13分26秒, Key ID 1c4cbdcdcd2efd2a

Related branches

Alexey Kopytov (akopytov) wrote :

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?

Ren Xiaolei (julyclyde) wrote :

At the end of execution, it says created a backup in the directory. So I walk through to see what's in it.
Just a minor bug.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-863

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers