Mtr against a standalone mysql-codership: innodb.innodb_prefix_index_restart_server

Bug #1358264 reported by Esa Kettunen on 2014-08-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.5
Undecided
Esa Kettunen
5.6
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/mtr-run-2014-08-14-a.txt

Amongst the bugs we find the following:

CURRENT_TEST: innodb.innodb_prefix_index_restart_server
mysqltest: At line 85: query 'INSERT INTO worklog5743 VALUES(REPEAT("b", 3500) , REPEAT("o", 3500))' failed: 1062: Duplicate entry 'bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb' for key 'PRIMARY'

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/aug/codership-mysql/mysql-test/var/log/innodb_prefix_index_restart_server.log

Analysis:
---------
Duplicate primary key where the keys should be UNIQUE.
Might have somethings to do with a shutdown/crash & restart?

Tags: mtr Edit Tag help
Seppo Jaakola (seppo-jaakola) wrote :

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.

Seppo Jaakola (seppo-jaakola) wrote :

The actual problem was that the pending transaction was not rolled back, and got implicitly committed in later phase. This happened because the error from net read was never handled in native mysql processing mode.
Fis is pushed in wsrep-5.6 in revision:
http://bazaar.launchpad.net/~codership/codership-mysql/5.6/revision/4125

Esa Kettunen (egge) wrote :

Fix verified by test run.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1715

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers