Bug #71580 FLUSH TABLES WITH READ LOCK hangs when many clients run SELECT FOR UPDATE twice

Submitted: 4 Feb 2014 9:02 Modified: 6 Feb 2014 17:01
Reporter: Sadao Hiratsuka Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Locking Severity:S2 (Serious)
Version:5.6.16, 5.5.36 OS:Any
Assigned to: CPU Architecture:Any
Tags: flush tables with read lock, select for update

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

  • On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
  • On windows use WinZip or a similar utility to split the large file
[4 Feb 2014 9:03] Sadao Hiratsuka
test program to reproduce problem

Attachment: ConcurrentSelectForUpdate.java (application/octet-stream, text), 1.83 KiB.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.038 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
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.