Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.0.10
-
None
-
None
-
standard Linux, using Debian packages from mariadb
Description
Because of a full disk, my master logged a large heap of "LOST" incident messages. I tried to auto-skip them, but that did not work.
MariaDB [(none)]> show variables like '%slave_skip%'; |
+------------------------+-------+ |
| Variable_name | Value |
|
+------------------------+-------+ |
| slave_skip_errors | 1590 |
|
| sql_slave_skip_counter | 0 |
|
+------------------------+-------+ |
2 rows in set (0.00 sec) |
MariaDB [(none)]> show slave status\G
|
Slave_SQL_Running: No |
Last_Errno: 1590
|
Last_Error: The incident LOST_EVENTS occured on the master. Message: error writing to the binary log |
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
Because of a full disk, my master logged a large heap of "LOST" incident messages. I tried to auto-skip them, but that did not work. MariaDB [(none)]> show variables like '%slave_skip%'; +------------------------+-------+ | Variable_name | Value | +------------------------+-------+ | slave_skip_errors | 1590 | | sql_slave_skip_counter | 0 | +------------------------+-------+ 2 rows in set (0.00 sec) MariaDB [(none)]> show slave status\G Slave_SQL_Running: No Last_Errno: 1590 Last_Error: The incident LOST_EVENTS occured on the master. Message: error writing to the binary log |
Because of a full disk, my master logged a large heap of "LOST" incident messages. I tried to auto-skip them, but that did not work. {code:sql} MariaDB [(none)]> show variables like '%slave_skip%'; +------------------------+-------+ | Variable_name | Value | +------------------------+-------+ | slave_skip_errors | 1590 | | sql_slave_skip_counter | 0 | +------------------------+-------+ 2 rows in set (0.00 sec) MariaDB [(none)]> show slave status\G Slave_SQL_Running: No Last_Errno: 1590 Last_Error: The incident LOST_EVENTS occured on the master. Message: error writing to the binary log {code} |
| Assignee | Elena Stepanova [ elenst ] |
| Attachment | mdev6180-bin.000001 [ 29400 ] | |
| Fix Version/s | 10.0.12 [ 15201 ] | |
| Assignee | Elena Stepanova [ elenst ] | Kristian Nielsen [ knielsen ] |
| Workflow | defaullt [ 39826 ] | MariaDB v2 [ 43050 ] |
| Fix Version/s | 10.0.13 [ 16000 ] | |
| Fix Version/s | 10.0.12 [ 15201 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
Here is a MySQL 5.6 patch that fixes this:
revision-id: frazer@mysql.com-20110314170916-ypgin17otj3ucx95
parent: andrei.elkin@oracle.com-20110314135544-xez4ef4e0rynbmy9
committer: Frazer Clement <frazer@mysql.com>
branch nick: mysql-trunk
timestamp: Mon 2011-03-14 17:09:16 +0000
message:
Bug#11799671 NOT POSSIBLE TO SKIP INCIDENT ERRORS
do_apply_event() for the Incident_log_event is enhanced to check whether
the event should be skipped.
Testcase rpl_skip_incident is added.
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Fix Version/s | 10.0.13 [ 16300 ] | |
| Fix Version/s | 10.0 [ 16000 ] |
| Workflow | MariaDB v2 [ 43050 ] | MariaDB v3 [ 64085 ] |
| Workflow | MariaDB v3 [ 64085 ] | MariaDB v4 [ 147845 ] |
Test case to reproduce it without full disk
(the binary log is attached, it was produced by MySQL 5.6 which creates LOST_EVENTS upon this scenario):
On MySQL 5.6, it fails if run in the usual way, and passes if run with --mysqld=--slave-skip-errors=1590. On MariaDB 10.0, it fails either way.
Put the attached log into mysql-test/std_data.
Run with --mysqld=--slave-skip-errors=1590
--source include/master-slave.inc--connection slaveSTOP SLAVE;--source include/wait_for_slave_to_stop.incRESET SLAVE;--connection masterRESET MASTER;--let $datadir = `SELECT @@datadir`--remove_file $datadir/master-bin.000001--copy_file $MYSQL_TEST_DIR/std_data/mdev6180-bin.000001 $datadir/master-bin.000001--save_master_pos--connection slaveSTART SLAVE;--let $slave_timeout = 5--source include/wait_for_slave_to_start.inc--sync_with_master