mirror of
https://github.com/MariaDB/server.git
synced 2025-02-02 12:01:42 +01:00
f3314e90e3
Some errors that cause the slave SQL thread to stop are not shown in the
Slave_SQL_Error column of "SHOW SLAVE STATUS". Instead, the error is only
in the server's error log.
That makes it difficult to analyze the error for the user. One example of an error
that stops the slave but is not shown by "SHOW SLAVE STATUS" is when @@global.init_slave
is set incorrectly (e.g., it contains something that is not valid SQL).
Three failures were not correctly reported:
1 - Failures during slave thread initialization
2 - Failures while initializing the relay log position right after
starting the slave thread.
3 - Failures while processing queries passed through the init_slave
option.
This patch fixes the issues by reporting the errors through relay-info->report.
18 lines
558 B
Text
18 lines
558 B
Text
stop slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
reset master;
|
|
reset slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
start slave;
|
|
stop slave;
|
|
reset slave;
|
|
SET GLOBAL debug= "d,simulate_io_slave_error_on_init,simulate_sql_slave_error_on_init";
|
|
start slave;
|
|
Reporting the following error: Failed during slave thread initialization
|
|
SET GLOBAL debug= "";
|
|
stop slave;
|
|
reset slave;
|
|
SET GLOBAL init_slave= "garbage";
|
|
start slave;
|
|
Reporting the following error: Slave SQL thread aborted. Can't execute init_slave query
|
|
SET GLOBAL init_slave= "";
|