MySQL Bugs: #25460: High concurrency MyISAM access causes severe mysqld crash.

Bug #25460	High concurrency MyISAM access causes severe mysqld crash.
Submitted:	8 Jan 2007 3:10	Modified:	15 Mar 2007 18:08
Reporter:	Jason Williams	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: General	Severity:	S1 (Critical)
Version:	5.0.27,5.1.11,5.1.14,5.1.15	OS:	Solaris (Solaris 10)
Assigned to:	Ingo Strüwing	CPU Architecture:	Any
Tags:	bfsm_2007_02_01, bfsm_2007_02_15, regression

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

This is the error log of the primary Solaris 10 SPARC (T2000) server exhibiting the error. There's multi. instances in the file.

Attachment: iss.node1-sqlcluster1.err (application/octet-stream, text), 24.80 KiB.

Error log of Solaris 10 X64 server we moved the DB to, and had the same error.

Attachment: iss.err (application/octet-stream, text), 12.88 KiB.

Error log for MySQL instance. Taken right after crash.

Attachment: 2R01181807_crash_iss.err (application/octet-stream, text), 864 bytes.

Backtrace output from GDB against core file and crashed mysqld binary.

Attachment: 2R01181807_crash_gdb-backtrace.txt (text/plain), 10.51 KiB.