Bug #55542 | 'Built-in InnoDB' <> 'InnoDB Plugin' data mismatches for SET and BLOB columns | ||
---|---|---|---|
Submitted: | 26 Jul 2010 1:31 | Modified: | 29 Jul 2010 1:30 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: InnoDB Plugin storage engine | Severity: | S1 (Critical) |
Version: | 5.1.49, 5.1.50 bzr | OS: | Any |
Assigned to: | Marko Mäkelä | CPU Architecture: | Any |
Tags: | randgen |
[26 Jul 2010 1:31]
Roel Van de Paar
[26 Jul 2010 1:38]
Roel Van de Paar
Issue can be reproduced without the LIMIT clauses also: update: UPDATE _table SET _field = digit WHERE condition ; delete: DELETE FROM _table WHERE condition ; # 2010-07-26T11:34:33 Query: DELETE FROM `table100_innodb_int_autoinc` WHERE `col_set_key` > '2007-02-17 13:36:56' AND `pk` < '2005-04-26 04:40:29' failed: affected_rows mismatch between servers (15 vs. 22) # 2010-07-26T11:34:51 Query: DELETE FROM `table100_innodb_int_autoinc` WHERE `pk` > 4 AND `col_blob` < 'come' failed: affected_rows mismatch between servers (17 vs. 13)
[26 Jul 2010 4:26]
Roel Van de Paar
See bug #55543
[26 Jul 2010 6:51]
Sveta Smirnova
Thank you for the report. Verified as described.
[29 Jul 2010 0:00]
Roel Van de Paar
OK, small mistake here: --threads=10 "--threads=N - number of threads to run. Using more than one thread makes the test non-deterministic. If 100% determinism is important (such as when running the same test against two servers) use either only SELECT queries or set --threads to 1. The default is 10 threads;" (http://forge.mysql.com/wiki/RandomQueryGenerator) However. I am still seeing issues with threads=1, but seems harder to reproduce. Uploading a log of at least one reproduce with threads=1 next.
[29 Jul 2010 1:30]
Roel Van de Paar
Not repeatable with --threads=1. I thought I had a log, was a mistake. Marking as not a bug.