MySQL Bugs: #91977: Dropping Large Table Causes Semaphore Waits; No Other Work Possible

Bug #91977	Dropping Large Table Causes Semaphore Waits; No Other Work Possible
Submitted:	11 Aug 2018 3:57
Reporter:	Jesper wisborg Krogh	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	5.7.17	OS:	Any
Assigned to:		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

drop or truncate large table will crash after long semaphore wait

Attachment: drop or truncate large table will crash after long semaphore wait.txt (text/plain), 200.84 KiB.

INNODB MONITOR OUTPUT

Attachment: monitor.txt (text/plain), 11.48 KiB.

Flamegraph of a idle databse when running drop (btr_drop_ahi_for_table hot) 8.0.30

Attachment: perf.report.out.svg (image/svg+xml, text), 675.12 KiB.