List:General Discussion« Previous MessageNext Message »
From:Rusma Mulyadi Date:May 5 2003 10:48pm
Subject:assertion failure
View as plain text  
Hi,

 

I am using load data infile to upload a 2 GB file into a MySQL 4.0.12 InnoDB
table.

 

After a few days of processing, it finally crashed with a bunch of warnings
and errors.

The following is the last part of the error log.

Is this because autocommit does not commit the transaction during a load
data infile? 

Please advice!

Thanks,

Rusma

 

030504 13:35:07  InnoDB: WARNING: over 4 / 5 of the buffer pool is occupied
by

InnoDB: lock heaps or the adaptive hash index! Check that your

InnoDB: transactions do not set too many row locks. Starting InnoDB

InnoDB: Monitor to print diagnostics, including lock heap and hash index

InnoDB: sizes.

030504 13:35:07  InnoDB: ERROR: over 9 / 10 of the buffer pool is occupied
by

InnoDB: lock heaps or the adaptive hash index!

InnoDB: We intentionally generate a seg fault to print a stack trace

InnoDB: on Linux!

030504 13:35:07  InnoDB: Assertion failure in thread 10 in file buf0lru.c
line 219

InnoDB: We intentionally generate a memory trap.

InnoDB: Send a detailed bug report to mysql@stripped

mysqld got signal 11;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

We will try our best to scrape up some info that will hopefully help
diagnose

the problem, but since we have already crashed, something is definitely
wrong

and this may fail.

 

key_buffer_size=8388600

read_buffer_size=131072

 


Thread
assertion failureRusma Mulyadi6 May
Re: assertion failureHeikki Tuuri6 May
  • RE: assertion failureRusma Mulyadi6 May
    • Re: assertion failureJeremy Zawodny6 May
  • RE: assertion failureRusma Mulyadi7 May
    • Re: assertion failureHeikki Tuuri7 May