| Bug #20312 | crash during stress testing, InnoDB, several PK updates within one transaction | ||
|---|---|---|---|
| Submitted: | 7 Jun 2006 9:36 | Modified: | 16 Mar 2007 19:13 |
| Reporter: | Matthias Leich | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 5.0 | OS: | |
| Assigned to: | Alexey Kopytov | CPU Architecture: | Any |
[7 Jun 2006 9:38]
Matthias Leich
stack trace
Attachment: stacktrace (application/octet-stream, text), 4.16 KiB.
[7 Jun 2006 9:39]
Matthias Leich
master.log
Attachment: masterlog.tgz (application/x-compressed-tar, text), 26.31 KiB.
[7 Jun 2006 9:39]
Matthias Leich
stress test configuration file
Attachment: innodb1.env (application/octet-stream, text), 7.49 KiB.
[7 Jun 2006 9:44]
Matthias Leich
Sorry, one correction ENG1, ENG2 and ENG_LOG are set to InnoDB
[15 Jun 2006 10:32]
Heikki Tuuri
This is probably not an InnoDB bug, as we see from the stack trace.

Description: QA stress testsuite "system_2": - ENG1=InnoDB , ENG2=MyISAM, ENG_LOG=MyISAM - A mixup of INSERT/UPDATE/DELETE/SELECT scripts is running in 10 client threads. - Some of the testscripts use stored procedures. - Triggers or FOREIGN KEYs do not exist. Crash after about 2 minutes runtime of the client threads. The crash appears during the processing of: UPDATE systest1.tb1_eng1 target SET i1 = (SELECT new_i1 FROM systest1.t1_tmp source WHERE source.i1 = target.i1), f1 = @connection_id, f2 = @operation, f3 = ROUND(i1/@max_val,3), f4 = @my_now WHERE i1 = @next_val + 6 - @no_of_tries DIV 2 This statement belongs to the transactional testscript tb1_eng1_upd10.test which performs several PRIMARY KEY (-->i1) updates within one transaction. Please have a look into the attached files (stacktrace, master.log, stress test configuration). My environment: - PC(Pentium M, x86-32Bit) with Linux(SuSE 9.3) - MySQL compiled (compile-pentium-debug-max) from source Version 5.0 ChangeSet@1.2173, 2006-06-06 How to repeat: Please - clone the internal QA tree bk-internal.mysql.com:/home/bk/mysql-test-extra-5.0 - cd <test_extra>/mysql-test/suite/system_2 - adjust the attached configuration file (innodb1.env) to your configuration (paths to files ...) - run nice -20 ./run_systest2 --config=innodb1.env - be patient, if you need several attempts to reproduce the crash.