|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: MySQL Innodb Crash on 2 concurrent select
From: Ady Wicaksono (ady.wicaksono
infokom.net)
Date: Thu Nov 17 2005 - 22:09:42 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ok greg,
I'll report this bug
Thx
Greg 'groggy' Lehey wrote:
>On Wednesday, 16 November 2005 at 20:40:35 +0700, Ady Wicaksono wrote:
>
>
>>I have MySQL with about 12 billion rows when i try to create 2
>>process, each select count(*) on the same table.... after a long
>>time about 30 minutes it crashed :(
>>
>>ANy information?
>>
>>...
>>
>>InnoDB: We intentionally generate a memory trap.
>>InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
>>InnoDB: If you get repeated assertion failures or crashes, even
>>InnoDB: immediately after the mysqld startup, there may be
>>InnoDB: corruption in the InnoDB tablespace. Please refer to
>>InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
>>InnoDB: about forcing recovery.
>>mysqld got signal 11;
>>
>>
>
>This is obviously a bug. I've just checked the bug database, but I
>don't see a report on it yet. Could you please enter one?
>
>Greg
>--
>Greg Lehey, Senior Software Engineer
>MySQL AB, http://www.mysql.com/
>Echunga, South Australia
>Phone: +61-8-8388-8286 Mobile: +61-418-838-708
>
>Are you MySQL certified? http://www.mysql.com/certification/
>
>
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]