About deadlock of FLUSH TABLES WITH READ LOCK in xtrabackup

I am using Xtrabackup.

Is there a backup method that does not use FLUSH TABLES WITH READ LOCK ?
I am using slave and multithread slave. A deadlock bug may occur.


Please tell me the way to avoid this bug.

Xtrabackup’s --backup-locks is enabled by default.
Do not lock Innodb’s DML?

xtrabackup will automatically use Backup Locks as a lightweight alternative to FLUSH TABLES WITH READ LOCK to copy non-InnoDB data to avoid blocking DML queries that modify InnoDB tables.

I am using MySQL Community Edition.

Hello there can I just check - are you actually encountering this bug or are you just trying to make sure that you don’t encounter it in the future?


I encountered this bug with mysqldump.
I am checking if I encounter the same bug with xtrabackup.
However, I think that using - safe - slave - backup option will not encounter. is it right?

Hi Yuji Fujihara

If you want to avoid locks then you should examine --no-lock https://www.percona.com/doc/percona-xtrabackup/LATEST/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex-no-lock
But likely what you should work towards is --safe-slave-backup https://www.percona.com/doc/percona-xtrabackup/LATEST/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex-safe-slave-backup

Thanks you!