8 messages in com.mysql.lists.javaLoss of connection is large InnoDB ta...
FromSent OnAttachments
Konrad Billewicz16 Aug 2005 07:19 
Jim Cant16 Aug 2005 18:38 
Konrad Billewicz17 Aug 2005 02:57 
Jim Cant17 Aug 2005 06:26 
Konrad Billewicz18 Aug 2005 06:36 
Ronald Klop23 Aug 2005 07:24 
A.J. Blanchard (ajblanch)28 Aug 2005 20:18 
tom-...@supanet.com29 Aug 2005 10:41 
Subject:Loss of connection is large InnoDB table select...
From:A.J. Blanchard (ajblanch) (ajbl@cisco.com)
Date:08/28/2005 08:18:22 PM
List:com.mysql.lists.java

Greetings to all,

Could someone explain the error below. The DB had become so fouled that we had to drop and recreate the entire DB. It was receiving burst of inserts from client machines in the order of 100,000+ in a matter of seconds and the delete rate was much slower on the server machine. It had to process the "events" to see if they made any sense.

mysql> select * from EVENT_QUEUE where id='1'; Empty set (44.83 sec)

===> this is good since we had long past and remove ID=1.

mysql> select * from EVENT_QUEUE; ERROR 2013 (HY000): Lost connection to MySQL server during query

Now I have learned that its *my bad* to use an InnoDB table for high volume inserts and deletes. However, I also have requirements to survive non-loss of data with a power outage. So MEMORY tables and easily corrupted MyISAM tables were out (or so I thought).

ID is an auto-increment primary key. I also am using stock settings since I only just found that great "DB Design and Tuning" book from MySQL.

Any and all suggestions welcome.

A. J.