Vladislav Vaintroub added a comment - 2018-04-18 18:00 - edited It does not hang, it waits for the current holder of global read lock to release the lock (unlock tables). Holding that lock for long time is an excellent way to stall many queries, and not just mariabackup. If you do not want mariabackup to do "flush tables with read lock", there is an option for it. there are also options for controlling "flush table with read lock" timeouts, and even more (like, forcefully killing sessions that take too long time)

Vladislav Vaintroub added a comment - 2018-04-19 16:23 You are missing UNLOCK TABLES in your mysql client session. FTWRL locks all tables. do not hold it for long. do UNLOCK TABLES, when you're ready with whatever you did under lock.

Vladislav Vaintroub added a comment - 2018-04-19 16:26 Alternatively, if you in any reason have to FTWRL in the session, and hold it, you can do backup with --no-locks

Zdravelina Sokolovska (Inactive) added a comment - 2018-04-20 14:49 the same occurs when do backup with --no-locks mariabackup --backup -u root -p1 --galera-info --no-locks --target-dir=/var/mariadb/backup/B1 [root@t4w5 ~]# mariabackup --backup -u roo t -p1 --galera-info --no-locks --target-d ir=/var/mariadb/backup/B0 180420 17:43:23 Connecting to MySQL server host: localhost, user: root, password: se t, port: not set, socket: not set Using server version 10.3.6-MariaDB mariabackup based on MariaDB server 10.3.6 -MariaDB Linux (x86_64) mariabackup: uses posix_fadvise(). mariabackup: cd to /var/lib/mysql/ mariabackup: open files limit requested 0, set to 1024 mariabackup: using the following InnoDB co nfiguration: mariabackup: innodb_data_home_dir = . mariabackup: innodb_data_file_path = ibd ata1:12M:autoextend mariabackup: innodb_log_group_home_dir = ./ 2018-04-20 17:43:23 0 [Note] InnoDB: Numbe r of pools: 1 mariabackup: Generating a list of tablespa ces 2018-04-20 17:43:23 0 [Warning] InnoDB: Al located tablespace ID 158 for vd/t, old ma ximum was 0 2018-04-20 17:43:23 0 [Warning] InnoDB: Op en files 61 exceeds the limit 184467440737 09551615 180420 17:43:23 >> log scanned up to (4821 3480709) 180420 17:43:23 [01] Copying ./ibdata1 to /var/mariadb/backup/B0/ibdata1 2018-04-20 17:43:24 0 [Warning] InnoDB: Op en files 62 exceeds the limit 184467440737 09551615 180420 17:43:24 >> log scanned up to (4821 3480709) 180420 17:43:25 [01] ...done 180420 17:43:25 [01] Copying ./vd/t.ibd to /var/mariadb/backup/B0/vd/t.ibd 180420 17:43:25 [01] ...done   ~~~~~~~~~ 180420 17:43:48 [01] Copying ./tpcc/STOCK. ibd to /var/mariadb/backup/B0/tpcc/STOCK.i bd 180420 17:43:49 [01] ...done 180420 17:43:49 [01] Copying ./tpcc/WAREHO USE.ibd to /var/mariadb/backup/B0/tpcc/WAR EHOUSE.ibd 180420 17:43:49 [01] ...done 180420 17:43:49 Executing FLUSH NO_WRITE_T O_BINLOG TABLES... 180420 17:43:49 Executing FLUSH TABLES WIT H READ LOCK... . mariabackup hangs

Vladislav Vaintroub added a comment - 2018-04-20 14:59 it does not hang, it waits, for lock holder to release the lock. and it does not work, because the option was mistyped (also in our documentation). it is called correctly --no-lock , not --no-locks