Bug #95115 mysqld deadlock of all client threads originating from 3-way deadlock
Submitted: 24 Apr 2019 17:16 Modified: 18 Jul 2019 13:18
Reporter: Sandeep Dube Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S1 (Critical)
Version:5.7.24 OS:CentOS (CentOS Linux release 7.6.1810 (Core))
Assigned to: CPU Architecture:x86 (x86_64, ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs)
Tags: deadlock, slave thread initialization

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:

[24 Apr 2019 17:18] Sandeep Dube
Complete discription with trace

Attachment: mysql_dedlock_trace.rtf (text/rtf), 20.84 KiB.

[24 Apr 2019 17:40] Sandeep Dube
Complete discription with trace pdf format

Attachment: mysql_dedlock_trace_pdf.pdf (application/pdf, text), 73.89 KiB.

[24 Apr 2019 17:46] Sandeep Dube
Complete discription with trace html

Attachment: mysql_dedlock_trace_html.html (text/html), 29.87 KiB.

[24 Apr 2019 17:56] Sandeep Dube
Complete discription with trace txt

Attachment: mysql_deadlock_trace_txt.txt (text/plain), 16.30 KiB.

[26 Apr 2019 0:57] Jacek Cencek
Small typo: at the very bottom, the 3rd label states 'THREAD 9775', which should be 'THREAD 14000'. Attaching fixed version

Attachment: backtraces.txt (text/plain), 16.30 KiB.

[7 May 2019 20:33] Leo Lin
thread dump of the same deadlock we've found

Attachment: thread_dump.txt (text/plain), 690.42 KiB.