Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-8345

STOP SLAVE should not cause an ERROR to be logged to the error log

Details

    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

        Activity

          ccalender Chris Calender (Inactive) created issue -
          elenst Elena Stepanova made changes -
          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
          elenst Elena Stepanova made changes -
          elenst Elena Stepanova made changes -
          elenst Elena Stepanova made changes -
          Fix Version/s 10.0 [ 16000 ]
          elenst Elena Stepanova made changes -
          Status Open [ 1 ] Confirmed [ 10101 ]
          serg Sergei Golubchik made changes -
          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
          serg Sergei Golubchik made changes -
          Assignee Sergei Golubchik [ serg ]
          serg Sergei Golubchik made changes -
          Status Confirmed [ 10101 ] In Progress [ 3 ]
          serg Sergei Golubchik made changes -
          Status In Progress [ 3 ] Stalled [ 10000 ]
          serg Sergei Golubchik made changes -
          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 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 70050 ] MariaDB v4 [ 149289 ]

          People

            serg Sergei Golubchik
            ccalender Chris Calender (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.