Mtr against a standalone mysql-codership: innodb.innodb_prefix_index_restart_server
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
Triaged
|
Undecided
|
Esa Kettunen | |||
5.6 |
Fix Released
|
Medium
|
Seppo Jaakola | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
New
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Running mysql standard test suite mtr against a standalone mysql with
codership patches:
./mtr --reorder --report-features --comment="Trying reorder, report-features" --mem --suite innodb --debug-server --no-warnings --force --max-test-fail=100 | tee /home/egge/
Amongst the bugs we find the following:
CURRENT_TEST: innodb.
mysqltest: At line 85: query 'INSERT INTO worklog5743 VALUES(REPEAT("b", 3500) , REPEAT("o", 3500))' failed: 1062: Duplicate entry 'bbbbbbbbbbbbbb
The result from queries just before the failure was:
< snip >
START TRANSACTION;
"In connection default ....restarting the server"
SELECT COUNT(*) FROM worklog5743;
COUNT(*)
2
SELECT col_1_text = REPEAT("a", 3500) , col_2_text = REPEAT("o", 3500) FROM
worklog5743;
col_1_text = REPEAT("a", 3500) col_2_text = REPEAT("o", 3500)
1 1
0 1
"In connection 1"
SELECT col_1_text = REPEAT("a", 3500) , col_2_text = REPEAT("o", 3500) FROM
worklog5743;
col_1_text = REPEAT("a", 3500) col_2_text = REPEAT("o", 3500)
1 1
0 1
SELECT COUNT(*) FROM worklog5743;
COUNT(*)
2
START TRANSACTION;
More results from queries before failure can be found in /home/egge/
Analysis:
---------
Duplicate primary key where the keys should be UNIQUE.
Might have somethings to do with a shutdown/crash & restart?
There was unfinished transaction at the time of shutdown, and duruing startup recovery, this transaction was committed. This resulted in duplicate key error with next insert statement.