| Bug #26930 | Falcon: Replaying a big mysql dump file crashes mysqld | ||
|---|---|---|---|
| Submitted: | 7 Mar 2007 18:54 | Modified: | 15 Jun 2007 8:30 |
| Reporter: | Hakan Küçükyılmaz | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Falcon storage engine | Severity: | S1 (Critical) |
| Version: | 5.1-Falcon | OS: | Any |
| Assigned to: | Christopher Powers | CPU Architecture: | Any |
[15 Jun 2007 8:30]
MC Brown
A note has been added to the 6.0.1 changelog.
Description: This test was running successfully with Falcon sometime last year. Replaying a fairly big mysql dump file crashes Falcon. How to repeat: On fluffy: hakan@fluffy:~> time zcat my1_extended_tinyblob2varbinary_255_for_jstar.sql.gz | mysql -uroot my1 ERROR 2013 (HY000) at line 183726: Lost connection to MySQL server during query Than after some time I see this in the log ------------------------------------ Stalled threads Thread 2aaaaba03730 (1084778848) sleep=0, grant=1, locks=0, who 1, javaThread 0 prior=2aaaab9f99a0, next=0, parent=2aaaab9d0000 Stalled synchronization objects: ------------------------------------ Stalled threads Thread 2aaaab9cf188 (1076373856) sleep=0, grant=0, locks=1, who 0 Number of processes running now: 0 070307 13:28:45 mysqld restarted