Xtrabackup never stop when exporting tables

Bug #1129930 reported by Frederic Descamps
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Expired
Undecided
Unassigned

Bug Description

When trying to export tables xtrabackup_55 never ends.

details:
--------

Version: 5.5.27-28.1-log Percona Server (GPL), Release rel28.1, Revision 296

Tables have the requested format (checked with innochecksum -f) : all selected tables have "Detected file format: Antelope (5.1.7 or newer)."

Backup was taken with :

innobackupex --defaults-file=/tmp/mysql.cnf --tables-file /tmp/lists.tables /mnt/data/tmp/

and the statement that hangs is :

xtrabackup_55 --prepare --export --innodb-file-per-table --target=2013-02-18_08-40-21/

The output is attached and strace is attached

The size is not that big:

[root@blogsdb01-2 2013-02-18_08-40-21]# ls -lh
total 7.3G
-rw-r--r-- 1 root root 263 Feb 18 08:40 backup-my.cnf
drwx------ 2 root root 4.0K Feb 18 09:25 XXX
-rw-r----- 1 root root 6.3G Feb 18 10:14 ibdata1
-rw-r----- 1 root root 1.1G Feb 18 10:14 ib_logfile0
-rw-rw---- 1 mysql mysql 36M Feb 18 09:01 ib_lru_dump
-rw-r--r-- 1 root root 13 Feb 18 09:01 xtrabackup_binary
-rw-r--r-- 1 root root 27 Feb 18 09:01 xtrabackup_binlog_info
-rw-r--r-- 1 root root 42 Feb 18 09:25 xtrabackup_binlog_pos_innodb
-rw-r----- 1 root root 89 Feb 18 09:01 xtrabackup_checkpoints

and in XXX :

[root@blogsdb01-2 2013-02-18_08-40-21]# ls -lh XXX/
total 46G
-rw-r--r-- 1 root root 16K Feb 18 09:25 XXX.exp
-rw-rw---- 1 mysql mysql 14K Sep 28 16:42 XXX.frm
-rw-r----- 1 root root 21G Feb 18 09:59 XXX.ibd
-rw-r--r-- 1 root root 16K Feb 18 09:25 XXY.exp
-rw-rw---- 1 mysql mysql 14K Sep 28 17:17 XXY.frm
-rw-r----- 1 root root 26G Feb 18 09:59 XXY.ibd
-rw-r--r-- 1 root root 16K Feb 18 09:25 XXZ.exp
-rw-rw---- 1 mysql mysql 8.5K Sep 28 17:56 XXZ.frm
-rw-r----- 1 root root 64M Feb 18 09:01 XXZ.ibd
-rw-r--r-- 1 root root 16K Feb 18 09:25 XYX.exp
-rw-rw---- 1 mysql mysql 8.6K Sep 28 17:56 XYX.frm
-rw-r----- 1 root root 29M Feb 18 09:01 XYX.ibd
-rw-r--r-- 1 root root 16K Feb 18 09:25 XYY.exp
-rw-rw---- 1 mysql mysql 8.7K Jan 31 23:34 XYY.frm
-rw-r----- 1 root root 96K Feb 18 09:25 XYY.ibd
-rw-r--r-- 1 root root 16K Feb 18 09:25 XYZ.exp
-rw-rw---- 1 mysql mysql 8.7K Sep 28 17:56 XYZ.frm
-rw-r----- 1 root root 1.0M Feb 18 09:25 XYZ.ibd

ps: table names were changed to keep data anonymous.

Revision history for this message
Frederic Descamps (lefred) wrote :

output of xtrabackup_55 and output of strace

Revision history for this message
Alexey Kopytov (akopytov) wrote :

InnoDB does a slow shutdown (i.e. full purge + change buffer merge) on --export, otherwise the tablespaces are not consistent and thus cannot be imported.

So all the usual performance considerations apply: sufficient buffer pool (i.e. --use-memory, 100MB by default) and fast enough storage.

Changed in percona-xtrabackup:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

Changed in percona-xtrabackup:
status: Incomplete → Expired
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.