Failure to write xtrabackup_suspended_2 file will leave backups running forever

[Jeremy Tinley]

Similar to https://bugs.launchpad.net/percona-xtrabackup/+bug/1007446

We were running multiple backups (different mysqld ports) on the same host, all with the same tmpdir. When one would write xtrabackup_suspended_2, another would warn that it couldn't write the same file. Obviously this can be prevented by unique tmpdirs, but this should ideally be fatal -- that is, it shouldn't keep reading the ibdata file forever.

[Nilnandan Joshi (nilnandan-joshi)]

Hi,

Checked with 2.2.10, xtrabackup_suspended_2 will be created in backup dir and not tmpdir

xtrabackup: Creating suspend file '/home/nilnandan/backup/2015-05-06_13-06-35/xtrabackup_suspended_2' with pid '11719'

In this case, it should not be issue to take multiple backups at the same time/host because it will create suspended file in backupdir which will be different. Can you please provide which xtrabackup version you are using? Also provide the output of multiple backups commands including warning. It might helpful to figure out this issue.

i.e xtrabackup --version

[Jeremy Tinley (techwolf359)]

This was version 2.2.8. I'll upgrade and my problem should go away.

This bug can be closed.

[Nilnandan Joshi (nilnandan-joshi)]

Even, I've checked with 2.2.8, and the same happening there that xtrabackup_suspended_2 will be created in backup dir.

xtrabackup: Creating suspend file '/home/nilnandan/backup/2015-05-07_09-18-44/xtrabackup_suspended_2' with pid '5875'

But still you can try to upgrade the version and check.

[Jeremy Tinley (techwolf359)]

I was going to the the opposite on this one. 2.2.10 still does it.

xtrabackup --defaults-group=mysqld --backup --suspend-at-end --target-dir=/var/tmp/mysql/3309 --datadir=/var/lib/mysql/ --innodb_log_file_size=536870912 --innodb_data_file_path=ibdata1:12M:autoextend --tmpdir=/var/tmp/mysql/3309 --compress --compress-threads=8 --extra-lsndir=/var/tmp/mysql/3309 --parallel=8 --stream=xbstream

Probably because of --target-dir

This still doesn't *really* cover the original case which was that if the file is added while the backup is in progress, it gets a non-fatal event and then continues scanning the logs.

[Shahriyar Rzayev (rzayev-sehriyar)]

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