Commit 7a789e20 authored by Sergei Golubchik's avatar Sergei Golubchik

sporadic failures of rpl.rpl_parallel_sbm

the test waits for the event to get stuck on MASTER_DELAY,
but on a slow/overloaded slave the event might pass MASTER_DELAY
before the test starts waiting.

Wait for the event to get stuck on the LOCK TABLES (after MASTER_DELAY),
the event cannot avoid that,
parent cea083af
...@@ -34,7 +34,7 @@ connection server_2; ...@@ -34,7 +34,7 @@ connection server_2;
LOCK TABLES t1 WRITE; LOCK TABLES t1 WRITE;
include/start_slave.inc include/start_slave.inc
connection slave; connection slave;
# Waiting for replica to resume the delay for the transaction # Waiting for replica to get blocked by the table lock
# Sleeping 1s to increment SBM # Sleeping 1s to increment SBM
# Ensuring Seconds_Behind_Master increases after sleeping.. # Ensuring Seconds_Behind_Master increases after sleeping..
# ..done # ..done
......
...@@ -77,8 +77,8 @@ LOCK TABLES t1 WRITE; ...@@ -77,8 +77,8 @@ LOCK TABLES t1 WRITE;
--source include/start_slave.inc --source include/start_slave.inc
--connection slave --connection slave
--echo # Waiting for replica to resume the delay for the transaction --echo # Waiting for replica to get blocked by the table lock
--let $wait_condition= SELECT count(*) FROM information_schema.processlist WHERE state LIKE 'Waiting until MASTER_DELAY seconds after master executed event'; --let $wait_condition= SELECT count(*) FROM information_schema.processlist WHERE state LIKE 'Waiting for table metadata lock';
--source include/wait_condition.inc --source include/wait_condition.inc
--echo # Sleeping 1s to increment SBM --echo # Sleeping 1s to increment SBM
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment