it seems that i cant pass --tmpdir to innobackupex.
Basically tmpdir is read from my.cnf tmpdir variable, right?
> Alexey Kopytov <email address hidden> kirjoitti 21.10.2013 kello 12.41:
>
> This is also not a recent regression -- the same limitation applies to
> 2.0, but it is unlikely it will be fixed in that branch.
>
> ** Changed in: percona-xtrabackup/2.1
> Status: New => Triaged
>
> ** Changed in: percona-xtrabackup/2.1
> Importance: Undecided => Medium
>
> ** Changed in: percona-xtrabackup/2.2
> Status: New => Triaged
>
> ** Changed in: percona-xtrabackup/2.2
> Importance: Undecided => Medium
>
> ** Also affects: percona-xtrabackup/2.0
> Importance: Undecided
> Status: New
>
> ** Changed in: percona-xtrabackup/2.0
> Status: New => Won't Fix
>
> ** Summary changed:
>
> - Xtrabackup 2.1.5 (since 2.1.4) leaves unfinished backups around
> + Concurrent XtraBackup instances fail with same --tmpdir
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1241987
>
> Title:
> Concurrent XtraBackup instances fail with same --tmpdir
>
> Status in Percona XtraBackup:
> Triaged
> Status in Percona XtraBackup 2.0 series:
> Won't Fix
> Status in Percona XtraBackup 2.1 series:
> Triaged
> Status in Percona XtraBackup 2.2 series:
> Triaged
>
> Bug description:
> Hey,
>
> I have a script that uses innobackupex to backup MariaDB 5.5.32 database instances (different datadirs and
> separate processes). One script per database instance.
>
> 2 backups had been scheduled to be run at the same time from 2 different instances at 1:00 AM
> I have rescheduled the backups to different times to see if it has any difference.
>
> Since 2.1.4 version, even in 2.1.5, backups sometimes don't get finished like normally
> and innobackupex returns an error code.
>
>
> innobackupex failed:
>
> ---------- ERROR OUTPUT from innobackupex ----------
>
> InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
> and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
>
> This software is published under
> the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
>
> 131019 01:00:01 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_file=/mariadb1/conf/my.cnf;mysql_read_default_group=xtrabackup' as 'root' (using password: YES).
> 131019 01:00:01 innobackupex: Connected to MySQL server
> IMPORTANT: Please check that the backup run completes successfully.
> At the end of a successful backup run innobackupex
> prints "completed OK!".
>
> innobackupex: Using mysql server version 5.5.32-MariaDB-log
>
> innobackupex: Created backup directory
> /mariadb1/backup/2013-10-19_01-00-01
>
> 131019 01:00:01 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-file="/mariadb1/conf/my.cnf" --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/mariadb1/backup/2013-10-19_01-00-01 --tmpdir=/var/tmp
> innobackupex: Waiting for ibbackup (pid=27051) to suspend
> innobackupex: Suspend file '/mariadb1/backup/2013-10-19_01-00-01/xtrabackup_suspended_2'
>
> xtrabackup_55 version 2.1.5 for Percona Server 5.5.31 Linux (x86_64) (revision id: 680)
> xtrabackup: uses posix_fadvise().
> xtrabackup: cd to /mariadb1/data
> xtrabackup: using the following InnoDB configuration:
> xtrabackup: innodb_data_home_dir = /mariadb1/data
> xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
> xtrabackup: innodb_log_group_home_dir = /mariadb1/data
> xtrabackup: innodb_log_files_in_group = 2
> xtrabackup: innodb_log_file_size = 134217728
> xtrabackup: using O_DIRECT
>>> log scanned up to (21810149)
> [01] Copying /mariadb1/data/ibdata1 to /mariadb1/backup/2013-10-19_01-00-01/ibdata1
> [01] ...done
>>> log scanned up to (21810149)
> xtrabackup: Creating suspend file '/mariadb1/backup/2013-10-19_01-00-01/xtrabackup_suspended_2' with pid '27051'
> print() on closed filehandle XTRABACKUP_PID at /mariabin/percona-xtrabackup/bin/innobackupex line 2602.
> 131019 01:00:03 innobackupex: Waiting for ibbackup (pid=27051) to finish
>
>
> So xtrabackup creates an suspend file, and innobackupex starts waiting on ibbackup.
> Then there's a print() on closed filehandle.
>
> When I check these processes they're no longer present during the day
> time.
>
> A bug or two backups cant run at the same time limitation in
> innobackupex?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-xtrabackup/+bug/1241987/+subscriptions
Hi,
it seems that i cant pass --tmpdir to innobackupex.
Basically tmpdir is read from my.cnf tmpdir variable, right?
> Alexey Kopytov <email address hidden> kirjoitti 21.10.2013 kello 12.41: xtrabackup/ 2.1 xtrabackup/ 2.1 xtrabackup/ 2.2 xtrabackup/ 2.2 xtrabackup/ 2.0 xtrabackup/ 2.0 /bugs.launchpad .net/bugs/ 1241987 ;mysql_ read_default_ file=/mariadb1/ conf/my. cnf;mysql_ read_default_ group=xtrabacku p' as 'root' (using password: YES). backup/ 2013-10- 19_01-00- 01 file="/ mariadb1/ conf/my. cnf" --defaults- group=" mysqld" --backup --suspend-at-end --target- dir=/mariadb1/ backup/ 2013-10- 19_01-00- 01 --tmpdir=/var/tmp backup/ 2013-10- 19_01-00- 01/xtrabackup_ suspended_ 2' data_home_ dir = /mariadb1/data data_file_ path = ibdata1: 10M:autoextend log_group_ home_dir = /mariadb1/data log_files_ in_group = 2 log_file_ size = 134217728 data/ibdata1 to /mariadb1/ backup/ 2013-10- 19_01-00- 01/ibdata1 backup/ 2013-10- 19_01-00- 01/xtrabackup_ suspended_ 2' with pid '27051' percona- xtrabackup/ bin/innobackupe x line 2602. /bugs.launchpad .net/percona- xtrabackup/ +bug/1241987/ +subscriptions
>
> This is also not a recent regression -- the same limitation applies to
> 2.0, but it is unlikely it will be fixed in that branch.
>
> ** Changed in: percona-
> Status: New => Triaged
>
> ** Changed in: percona-
> Importance: Undecided => Medium
>
> ** Changed in: percona-
> Status: New => Triaged
>
> ** Changed in: percona-
> Importance: Undecided => Medium
>
> ** Also affects: percona-
> Importance: Undecided
> Status: New
>
> ** Changed in: percona-
> Status: New => Won't Fix
>
> ** Summary changed:
>
> - Xtrabackup 2.1.5 (since 2.1.4) leaves unfinished backups around
> + Concurrent XtraBackup instances fail with same --tmpdir
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Concurrent XtraBackup instances fail with same --tmpdir
>
> Status in Percona XtraBackup:
> Triaged
> Status in Percona XtraBackup 2.0 series:
> Won't Fix
> Status in Percona XtraBackup 2.1 series:
> Triaged
> Status in Percona XtraBackup 2.2 series:
> Triaged
>
> Bug description:
> Hey,
>
> I have a script that uses innobackupex to backup MariaDB 5.5.32 database instances (different datadirs and
> separate processes). One script per database instance.
>
> 2 backups had been scheduled to be run at the same time from 2 different instances at 1:00 AM
> I have rescheduled the backups to different times to see if it has any difference.
>
> Since 2.1.4 version, even in 2.1.5, backups sometimes don't get finished like normally
> and innobackupex returns an error code.
>
>
> innobackupex failed:
>
> ---------- ERROR OUTPUT from innobackupex ----------
>
> InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
> and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
>
> This software is published under
> the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
>
> 131019 01:00:01 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:
> 131019 01:00:01 innobackupex: Connected to MySQL server
> IMPORTANT: Please check that the backup run completes successfully.
> At the end of a successful backup run innobackupex
> prints "completed OK!".
>
> innobackupex: Using mysql server version 5.5.32-MariaDB-log
>
> innobackupex: Created backup directory
> /mariadb1/
>
> 131019 01:00:01 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-
> innobackupex: Waiting for ibbackup (pid=27051) to suspend
> innobackupex: Suspend file '/mariadb1/
>
> xtrabackup_55 version 2.1.5 for Percona Server 5.5.31 Linux (x86_64) (revision id: 680)
> xtrabackup: uses posix_fadvise().
> xtrabackup: cd to /mariadb1/data
> xtrabackup: using the following InnoDB configuration:
> xtrabackup: innodb_
> xtrabackup: innodb_
> xtrabackup: innodb_
> xtrabackup: innodb_
> xtrabackup: innodb_
> xtrabackup: using O_DIRECT
>>> log scanned up to (21810149)
> [01] Copying /mariadb1/
> [01] ...done
>>> log scanned up to (21810149)
> xtrabackup: Creating suspend file '/mariadb1/
> print() on closed filehandle XTRABACKUP_PID at /mariabin/
> 131019 01:00:03 innobackupex: Waiting for ibbackup (pid=27051) to finish
>
>
> So xtrabackup creates an suspend file, and innobackupex starts waiting on ibbackup.
> Then there's a print() on closed filehandle.
>
> When I check these processes they're no longer present during the day
> time.
>
> A bug or two backups cant run at the same time limitation in
> innobackupex?
>
> To manage notifications about this bug go to:
> https:/