Add an option to disable opening all tablespaces on backup start

Bug #1222062 reported by Alexey Kopytov on 2013-09-07
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
High
Sergei Glushchenko
2.0
Won't Fix
High
Unassigned
2.1
Fix Released
High
Sergei Glushchenko
2.2
Fix Released
High
Sergei Glushchenko

Bug Description

As the discussion in #1183322 has shown, the fix for bug #1079700 introduces a problem for users with huge numbers of InnoDB tablespaces, and the workaround of raising the open files limits doesn't work in all cases due to a limitation in the Linux kernel.

So the only possible solution for that problem is to introduce another option to innobackupex/xtrabackup that would disable that functionality with a caveat that using that option may result in a broken backup if DDL is performed on InnoDB tables during the backup procedure.

Related branches

Although opening millions of files is just BAD BAD BAD, Linux doesn't really prevent you.

If you want to shoot that foot and permit 10 million open file descriptors, the following commands run as root may "help" you.

nfiles=10000000
sysctl fs.nr_open=$nfiles
ulimit -n $nfiles

tags: added: i44337

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

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

Other bug subscribers