| 2014-09-05 15:00:34 |
Davi Arnaut |
bug |
|
|
added bug |
| 2014-11-04 10:47:10 |
Alexey Kopytov |
nominated for series |
|
percona-xtrabackup/2.2 |
|
| 2014-11-04 10:47:10 |
Alexey Kopytov |
bug task added |
|
percona-xtrabackup/2.2 |
|
| 2014-11-04 10:47:19 |
Alexey Kopytov |
percona-xtrabackup/2.2: milestone |
|
2.2.7 |
|
| 2014-11-04 10:47:25 |
Alexey Kopytov |
percona-xtrabackup/2.2: status |
New |
Triaged |
|
| 2014-11-04 10:47:28 |
Alexey Kopytov |
percona-xtrabackup/2.2: importance |
Undecided |
Medium |
|
| 2014-11-04 10:47:31 |
Alexey Kopytov |
percona-xtrabackup/2.2: assignee |
|
Alexey Kopytov (akopytov) |
|
| 2014-11-14 05:15:28 |
Sergei Glushchenko |
percona-xtrabackup/2.3: milestone |
2.2.7 |
future-2.3-releases |
|
| 2014-11-28 12:09:04 |
Alexey Kopytov |
tags |
|
contribution |
|
| 2014-11-28 12:11:43 |
Alexey Kopytov |
percona-xtrabackup/2.2: status |
Triaged |
Fix Committed |
|
| 2014-11-28 12:11:48 |
Alexey Kopytov |
branch linked |
|
lp:~akopytov/percona-xtrabackup/bug1366065-2.2 |
|
| 2014-11-28 12:13:41 |
Alexey Kopytov |
percona-xtrabackup/2.3: status |
Triaged |
Fix Committed |
|
| 2014-11-28 12:13:53 |
Alexey Kopytov |
branch linked |
|
lp:~akopytov/percona-xtrabackup/bug1366065-2.3 |
|
| 2014-11-28 15:55:15 |
Alexey Kopytov |
percona-xtrabackup/2.2: status |
Fix Committed |
Fix Released |
|
| 2014-11-28 15:55:18 |
Alexey Kopytov |
percona-xtrabackup/2.3: status |
Fix Committed |
Fix Released |
|
| 2015-05-15 01:39:08 |
Sergei Glushchenko |
percona-xtrabackup/2.3: milestone |
future-2.3-releases |
2.3.1-beta1 |
|
| 2018-03-17 23:00:37 |
Davi Arnaut |
description |
XtraBackup is quite efficient at exporting tables from a backup when it contains a large change buffer (aka insert buffer) that is mostly composed of changes to tables other than the tables being exported.
The problem arises from the need to merge change buffer entries when exporting tables. In order to accomplish this, XtraBackup relies on a normal InnoDB shutdown that merges pending change buffer entries. The problem is that this background merging does random dives into the change buffer index (see ibuf_merge_pages), making the process rather inefficient if most of the entries in the change buffer are for tables that are not even part of the backup.
An easy solution is to simply discard all change buffer entries for an inexistent (deleted) tablespace once the first entry for such tablespace is found. Ideally and if possible, make export akin to FLUSH TABLES FOR EXPORT and do a fast shutdown. |
XtraBackup is quite inefficient at exporting tables from a backup when it contains a large change buffer (aka insert buffer) that is mostly composed of changes to tables other than the tables being exported.
The problem arises from the need to merge change buffer entries when exporting tables. In order to accomplish this, XtraBackup relies on a normal InnoDB shutdown that merges pending change buffer entries. The problem is that this background merging does random dives into the change buffer index (see ibuf_merge_pages), making the process rather inefficient if most of the entries in the change buffer are for tables that are not even part of the backup.
An easy solution is to simply discard all change buffer entries for an inexistent (deleted) tablespace once the first entry for such tablespace is found. Ideally and if possible, make export akin to FLUSH TABLES FOR EXPORT and do a fast shutdown. |
|
