Details
-
Type:
Bug
-
Status: In Progress
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 10.0.20, 10.1.6
-
Component/s: Replication, Tests
-
Labels:None
-
Sprint:10.1.6-2, 10.0.21
Description
rpl.rpl_000011 'row' w1 [ fail ]
Test ended at 2015-06-10 17:26:28
CURRENT_TEST: rpl.rpl_000011
— /usr/share/mysql/mysql-test/suite/rpl/r/rpl_000011.result 2015-06-10 13:40:30.000000000 +0300
+++ /run/shm/var/1/log/rpl_000011.reject 2015-06-10 17:26:28.339504149 +0300
@@ -8,7 +8,7 @@
stop slave;
show global status like 'com_insert';
Variable_name Value
-Com_insert 1
+Com_insert 2
include/wait_for_slave_to_stop.inc
start slave;
include/wait_for_slave_to_start.inc
mysqltest: Result content mismatch
Fails sporadically, but on many hosts.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
So this turns out to actually be an old bug.
It just happened to trigger more easily after patch for
MDEV-8294.The race is that there is a small window where SHOW GLOBAL STATUS may count
twice the values of a thread that is exiting. This happens also for normal
threads, not just the slave thread.
Here is a test case for latest 10.0, triggers with the following sleep
patched in:
The first SHOW GLOBAL STATUS counts the thread twice: