Bug #89331 Changing lock/release order in group commit causes a deadlock

Submitted: 20 Jan 2018 0:36 Modified: 14 Feb 2018 17:02
Reporter: Aliaksei Sandryhaila Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:8.0.3 OS:Red Hat
Assigned to: Venkatesh Duggirala CPU Architecture:Any

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
[22 Jan 2018 13:22] Umesh Shastry
rpl_nogtid suit test results after applying patch on top of 8.0.3 - 020025d9f277fd3283b8c75024f590857f58fbbd

Attachment: 89331_build.results (application/octet-stream, text), 40.51 KiB.

[24 Jan 2018 20:05] Aliaksei Sandryhaila
Minimal patch to reproduce the reported issue

Attachment: patch.diff (application/octet-stream, text), 2.39 KiB.

[25 Jan 2018 10:14] Umesh Shastry
test results

Attachment: 89331_latest.results (application/octet-stream, text), 417.68 KiB.

[5 Feb 2018 19:02] Aliaksei Sandryhaila
Modified patch to avoid deadlock

Attachment: modified_patch.txt (text/plain), 2.97 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.