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 ] |
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 ] |