Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.19, 10.1.5
-
Linux, Windows
Description
If you issue a STOP SLAVE on any slave (tested on 10.0.19 and 10.1.5), you will see an "ERROR" logged to the error log:
mysql> select version();
|
+----------------+
|
| version() |
|
+----------------+
|
| 10.1.5-MariaDB |
|
+----------------+
|
1 row in set (0.00 sec)
|
|
|
mysql> stop slave;
|
Query OK, 0 rows affected (0.10 sec)
|
Error log:
015-06-19 16:39:06 2496 [Note] Error reading relay log event: slave SQL thread was killed
|
2015-06-19 16:39:07 3508 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
|
2015-06-19 16:39:07 3508 [Note] Slave I/O thread killed while reading event
|
2015-06-19 16:39:07 3508 [Note] Slave I/O thread exiting, read up to log 'chris-laptop-bin.000008', position 120
|
The "[Note]"s are fine, but the "[Error]" is not. It then causes monitoring soulutions (MONyog, et al) to then issue alerts.
The same happens in MySQL, but it is fixed in 5.7.0:
https://bugs.mysql.com/bug.php?id=61275
It would be nice if we could fix this for 10.0 and 10.1, however.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Component/s | Replication [ 10100 ] | |
| Fix Version/s | 10.1 [ 16100 ] | |
| Description |
If you issue a STOP SLAVE on any slave (tested on 10.0.19 and 10.1.5), you will see an "ERROR" logged to the error log: mysql> select version(); +----------------+ | version() | +----------------+ | 10.1.5-MariaDB | +----------------+ 1 row in set (0.00 sec) mysql> stop slave; Query OK, 0 rows affected (0.10 sec) Error log: 015-06-19 16:39:06 2496 [Note] Error reading relay log event: slave SQL thread was killed 2015-06-19 16:39:07 3508 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013) 2015-06-19 16:39:07 3508 [Note] Slave I/O thread killed while reading event 2015-06-19 16:39:07 3508 [Note] Slave I/O thread exiting, read up to log 'chris-laptop-bin.000008', position 120 The "[Note]"s are fine, but the "[Error]" is not. It then causes monitoring soulutions (MONyog, et al) to then issue alerts. The same happens in MySQL, but it is fixed in 5.7.0: https://bugs.mysql.com/bug.php?id=61275 It would be nice if we could fix this for 10.0 and 10.1, however. |
If you issue a STOP SLAVE on any slave (tested on 10.0.19 and 10.1.5), you will see an "ERROR" logged to the error log: {noformat} mysql> select version(); +----------------+ | version() | +----------------+ | 10.1.5-MariaDB | +----------------+ 1 row in set (0.00 sec) mysql> stop slave; Query OK, 0 rows affected (0.10 sec) {noformat} Error log: {noformat} 015-06-19 16:39:06 2496 [Note] Error reading relay log event: slave SQL thread was killed 2015-06-19 16:39:07 3508 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013) 2015-06-19 16:39:07 3508 [Note] Slave I/O thread killed while reading event 2015-06-19 16:39:07 3508 [Note] Slave I/O thread exiting, read up to log 'chris-laptop-bin.000008', position 120 {noformat} The "[Note]"s are fine, but the "[Error]" is not. It then causes monitoring soulutions (MONyog, et al) to then issue alerts. The same happens in MySQL, but it is fixed in 5.7.0: https://bugs.mysql.com/bug.php?id=61275 It would be nice if we could fix this for 10.0 and 10.1, however. |
| Labels | upstream-fixed |
| Remote Link | This issue links to "Bug #61275 - Error in err file of slave, when stopping IO thread (Web Link)" [ 23709 ] |
| Remote Link | This issue links to "Bug #53955 - Error 2013 + "Error reading relay log event" on STOP SLAVE in Windows (Web Link)" [ 23710 ] |
| Fix Version/s | 10.0 [ 16000 ] |
| Status | Open [ 1 ] | Confirmed [ 10101 ] |
To me (looking at another log) it seams this error pops up before killing the IO thread instead of after killing the SQL thread.
Did anyone say that it has anything to do with SQL thread? I don't see anything like that here.
The error happens after the command STOP SLAVE (or STOP SLAVE IO_THREAD) is issued, and yes, it's logged right before the message about this thread being actually killed, which happens upon the STOP command.
| Summary | STOP SLAVE should note cause an ERROR to be logged to the error log | STOP SLAVE should not cause an ERROR to be logged to the error log |
| Assignee | Sergei Golubchik [ serg ] |
| Status | Confirmed [ 10101 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Stalled [ 10000 ] |
| Fix Version/s | 10.0.28 [ 22107 ] | |
| Fix Version/s | 10.1.19 [ 22111 ] | |
| Fix Version/s | 10.0 [ 16000 ] | |
| Fix Version/s | 10.1 [ 16100 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 70050 ] | MariaDB v4 [ 149289 ] |
So-called "internally filed bug", which Bug #61275 refers to, is in fact Bug #53955 - Error 2013 + "Error reading relay log event" on STOP SLAVE in Windows.
Here is the commit comment for this bugfix:
commit 6b24763a834f14e754afca9a259ca6251c4f4b4c 2e8de7fa9dada2d0b881b55a64f3228a2742d7aaAuthor: Manish Kumar <manish.4.kumar@oracle.com>Date: Tue Mar 27 13:10:42 2012 +0530BUG#12977988 - ON STOP SLAVE: ERROR READING PACKET FROM SERVER: LOST CONNECTIONTO MYSQL SERVERBUG#11761457 - ERROR 2013 + "ERROR READING RELAY LOG EVENT" ON STOP SLAVE IN WINDOWSProblem - on STOP SLAVE, the slave reliably produces the record in the error log[ERROR] Error reading packet from server: Lost connection to MySQLserver during query (server_errno=2013)There is not negative effect of this error being logged to the errorlog file.Fix - after execution of STOP SLAVE we check for the value of mi->rli->abort_slave.This flag is used to suppress any error or warning messages that we getduring execution. So if the flag is set it means we can ignore the error anddo not log it in the error log.