MySQL Forums
Forum List  »  NDB clusters

Re: Waiting for commit lock
Posted by: Mikael Ronström
Date: July 14, 2017 05:51PM

Here is a cut from the manual on how mysqldump works:

This backup operation acquires a global read lock on all tables at the beginning of the dump (using FLUSH TABLES WITH READ LOCK). As soon as this lock has been acquired, the binary log coordinates are read and the lock is released. If long updating statements are running when the FLUSH statement is issued, the backup operation may stall until those statements finish. After that, the dump becomes lock-free and does not disturb reads and writes on the tables.

So during the entire backup operation the entire MySQL Server is
locked such that you can only read data.

This affects also NDB tables since it locks the entire MySQL Server.

So this is the reason why you get this lock.

Backups of NDB data is fully online and requires no locks for read and
write of data. So it is obviously necessary here to consider how you want
to backup non-NDB data in the MySQL Servers used for accessing MySQL Cluster

Options: ReplyQuote

Written By
July 12, 2017 03:27AM
July 12, 2017 07:16AM
July 14, 2017 12:03PM
Re: Waiting for commit lock
July 14, 2017 05:51PM
July 16, 2017 03:19AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.