holland-coredev team mailing list archive

[Andrew Garner <766676@xxxxxxxxxxxxxxxxxx>]

I added a lockless-only = yes|no option to mysqldump in my amsterdam
(holland1.1) tree here:

https://github.com/abg/holland/blob/amsterdam/plugins/holland.backup.mysqldump/holland/backup/mysqldump/spec.py

This will abort the backup if holland-mysqldump would use --lock-tables
(i.e. a table in some non-excluded database is non-transactional).  This
will output something like:

[ERROR] Database 'test' has one or more non-transactional tables:
[ERROR]   * test.foo is non-transactional (engine=MyISAM)
[INFO] Backup 'mysqldump' failed: One or more databases had non-transactional tables that would result in a locking backup but lockless-only was requested.  Aborting backup.

-- 
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/766676

Title:
  Require lockless backup

Status in Holland Backup Framework:
  In Progress

Bug description:
  It would be nice to have an option where you require that the backup
  fail if it can not be completed without locking. There are cases where
  I would rather have no backup for the night than downtime.

  An example would be a database which is pure innodb having a new table
  accidentally created as MyISAM. Ordinarily this would just downgrade
  from --single-transaction to --lock-tables but it would be nice to
  have an option where instead the backup refuses to start until the
  table is converted to a transactional engine.