Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1.20
-
openSUSE 42.2
Linux 4.4.36-8-default #1 SMP Fri Dec 9 16:18:38 UTC 2016 (3ec5648) x86_64 x86_64 x86_64 GNU/Linux
MariaDB
Version : 10.1.20-2.1
Arch : x86_64
Vendor : obs://build.opensuse.org/server:database
Description
Since we changed from MySQL to MariDB 10.1.20 we expecting data integrity problems. Some deeper investigations aproved that fact and we would have a resolution for this Problem:
In our test case we have two nodes connected over lan and have a typical replication between them:
SystemA <---> SystemB
From SystemC we have started mysqlslap on SystemA to generate some queries:
CREATE DATABASE perftest; |
CREATE TABLE perftest.a (ID int NOT NULL AUTO_INCREMENT, b TEXT, PRIMARY KEY (ID)) ENGINE=MyISAM; |
mysqlslap -h SystemA -p --delimiter=";" --query="INSERT INTO perftest.a (b) VALUES(NOW())" --concurrency=500 --iterations=200 |
In the meantime of the generation we stopped on SystemB the slave and started after some seconds again
stop slave;
|
start slave;
|
We are waiting a while until SystemA has a count of 100000 inserts = mysqlslap has finished the generation:
select count(*) from perftest.a; |
Repeat the above count on SystemB(Slave) where we have stopped and started the slave, you will see a huge difference. In other words, we have a data loss!