Bug #39661 | Assert in SerialLogWindow.cpp during very long lasting insert transaction | ||
---|---|---|---|
Submitted: | 26 Sep 2008 9:30 | Modified: | 1 Sep 2009 7:42 |
Reporter: | Olav Sandstå | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S2 (Serious) |
Version: | 6.0.7 | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | F_MEMORY |
[26 Sep 2008 9:30]
Olav Sandstå
[28 Sep 2008 13:28]
Olav Sandstå
Some additional observations about the crash: 1. The client exited with the following error message from the server: Sep 26, 2008 2:16:06 AM LoadData main SEVERE: null java.sql.SQLException: Got error 305 'record memory is exhausted' from Falcon 2. The server crash/assert occurred over one hour after the client had exited. 3. After the crash, Falcon is unable to recover: 080926 03:28:54 mysqld_safe mysqld restarted New table space FALCON_USER, id 1, type 0, filename falcon_user.fts New table space FALCON_TEMPORARY, id 2, type 0, filename falcon_temporary.fts 080926 3:29:52 [ERROR] Falcon: Recovery failed: corrupted serial log 080926 3:29:52 [ERROR] Plugin 'Falcon' init function returned error. 080926 3:29:52 [ERROR] Plugin 'Falcon' registration as a STORAGE ENGINE failed. 080926 3:29:52 InnoDB: Started; log sequence number 0 46409 080926 3:29:52 [ERROR] Unknown/unsupported table type: falcon 080926 3:29:52 [ERROR] Aborting
[28 Sep 2008 15:18]
Olav Sandstå
Load client used for reproducing the crash
Attachment: LoadData.java (text/x-java), 3.86 KiB.
[28 Sep 2008 15:30]
Olav Sandstå
Verified that the crash is reproducable using the included test client. Falcon is compiled with Sun Studio 12 and running on Solaris 10 MU2 server. Falcon is configured with 10 GB of record cache and 8 GB page cache.