mirror of
https://github.com/MariaDB/server.git
synced 2025-08-26 01:44:06 +03:00
595a007d4e
SCAN/CPU) => SLAVE FAILURE When a statement containing a large amount of ROWs to be applied on the slave, and the slave's table does not contain a PK, it can take a considerable amount of time to find and change all the rows that are to be changed. The proper slave enhancement will be implemented in WL 5597. However, in this bug we are making it clear to the user what the problem is, by printing a message to the error log if the execution time, for a given statement in RBR, takes more than LONG_FIND_ROW_THRESHOLD (set to 60 seconds). This shall help the DBA to diagnose what's happening when facing a slave server that is quiet for no apparent reason... The note is only printed to the error log if log_warnings is set to be greater than 1.
19 lines
533 B
Plaintext
19 lines
533 B
Plaintext
include/master-slave.inc
|
|
[connection master]
|
|
include/stop_slave.inc
|
|
SET GLOBAL log_warnings = 2;
|
|
SET GLOBAL debug="d,inject_long_find_row_note";
|
|
include/start_slave.inc
|
|
CREATE TABLE t1 (c1 INT);
|
|
INSERT INTO t1 VALUES (1), (2);
|
|
UPDATE t1 SET c1= 1000 WHERE c1=2;
|
|
DELETE FROM t1;
|
|
DROP TABLE t1;
|
|
# Check if any note related to long DELETE_ROWS and UPDATE_ROWS appears in the error log
|
|
Occurrences: update=1, delete=1
|
|
include/stop_slave.inc
|
|
SET GLOBAL debug = '';
|
|
SET GLOBAL log_warnings = 1;
|
|
include/start_slave.inc
|
|
include/rpl_end.inc
|