Bug #79504 | STOP SLAVE IO THREAD prints wrong LOST CONNECTION message in error log file. | ||
---|---|---|---|
Submitted: | 3 Dec 2015 10:00 | Modified: | 29 Mar 2016 20:59 |
Reporter: | Venkatesh Duggirala | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.5 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[3 Dec 2015 10:00]
Venkatesh Duggirala
[29 Mar 2016 20:59]
Daniel So
Added the following entry to the server 5.6.30, 5.7.12, and 5.8.0 changelogs: "Issuing STOP SLAVE caused a spurious Error reading packet from server: Lost connection to MySQL server during query message to be written to the error log. With this fix, when connection to the master is lost, the abort_slave flag is checked and the error message is printed only if the flag is not set."