Bugs - Deadlocked Slave When Running SHOW/KILL/STOP SLAVE Commands.
(Doc ID 1588518.1)
Last updated on APRIL 06, 2020
Applies to:MySQL Server - Version 5.5 to 5.7 [Release 5.5 to 5.7]
Information in this document applies to any platform.
Slave server can become totally deadlocked and hang when executing certain SHOW or STOP SLAVE commands.
Command hangs/deadlocks have been seen and often involve one or more of the following:
o) MTS (Multi thread slave) had some deadlocks in older versions of 5.6.
o) FLUSH TABLES WITH READ LOCK may have been executed first.
o) SHOW PROCESSLIST
o) SHOW SLAVE STATUS
o) STOP SLAVE/START SLAVE
o) SHOW MASTER LOGS
o) binary log rotation caused by PURGE MASTER LOG,S or max_binlog_size was hit, or expire_logs_days is set.
o) A reconnecting slave who tries to KILL zombie slaves.
o) Privileges operations (CREATE USER, GRANT, etc).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document