mirror of
https://github.com/MariaDB/server.git
synced 2025-08-07 00:04:31 +03:00
567c097359
Warnings are added to net_server.cc when global_system_variables.log_warnings >= 4. When the above condition holds then: - All communication errors from net_serv.cc is also written to the error log. - In case of a of not being able to read or write a packet, a more detailed error is given. Other things: - Added detection of slaves that has hangup to Ack_receiver::run() - vio_close() is now first marking the socket closed before closing it. The reason for this is to ensure that the connection that gets a read error can check if the reason was that the socket was closed. - Add a new state to vio to be able to detect if vio is acive, shutdown or closed. This is used to detect if socket is closed by another thread. - Testing of the new warnings is done in rpl_get_lock.test - Suppress some of the new warnings in mtr to allow one to run some of the tests with -mysqld=--log-warnings=4. All test in the 'rpl' suite can now be run with this option. - Ensure that global.log_warnings are restored at test end in a way that allows one to use mtr --mysqld=--log-warnings=4. Reviewed-by: <serg@mariadb.org>,<brandon.nesterenko@mariadb.com>
25 lines
925 B
Plaintext
25 lines
925 B
Plaintext
include/master-slave.inc
|
|
[connection master]
|
|
connection slave;
|
|
include/stop_slave.inc
|
|
SET @saved_dbug = @@GLOBAL.debug_dbug;
|
|
SET GLOBAL log_warnings = 2;
|
|
SET GLOBAL debug_dbug="d,inject_long_find_row_note";
|
|
include/start_slave.inc
|
|
connection master;
|
|
CREATE TABLE t1 (c1 INT);
|
|
connection slave;
|
|
connection master;
|
|
INSERT INTO t1 VALUES (1), (2);
|
|
UPDATE t1 SET c1= 1000 WHERE c1=2;
|
|
DELETE FROM t1;
|
|
DROP TABLE t1;
|
|
connection slave;
|
|
# Check if any note related to long DELETE_ROWS and UPDATE_ROWS appears in the error log
|
|
FOUND 1 /The slave is applying a ROW event on behalf of an UPDATE statement on table t1 and is currently taking a considerable amount/ in mysqld.2.err
|
|
FOUND 1 /The slave is applying a ROW event on behalf of a DELETE statement on table t1 and is currently taking a considerable amount/ in mysqld.2.err
|
|
include/stop_slave.inc
|
|
SET @@GLOBAL.debug_dbug = @saved_dbug;
|
|
include/start_slave.inc
|
|
include/rpl_end.inc
|