Richard,
----- Original Message -----
From: "Richard F. Rebel" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, June 04, 2003 7:50 PM
Subject: Re: RH 8.0 InnoDB: Assertion failure in thread 122911 in
filemem0pool.c line 477
> Hello Heikki,
>
> Sorry, last version of the MySQL-Max rpm was missing the symbols file.
> This version has it, so I did as you asked. Here is the output of the
> most recent 4.
the memory deallocation seems to happen usually in
"
if (prebuilt->blob_heap != NULL) {
mem_heap_free(prebuilt->blob_heap);
prebuilt->blob_heap = NULL;
}
"
select MEET, count(*)
from RATINGS_WHENU
where MEET in ('N','Y')
and SITE = '63'
group by MEET
You have BLOBs in the table? How big are they? What does SHOW CREATE TABLE
give as the table definition?
What is really strange in the assertion failures on line 372 is that the hex
dump does show the memory block IS marked free:
"
InnoDB: Error: Removing element from mem pool free list 7 though the
InnoDB: element is not marked free! Dump of 100 bytes around element:
len 100; hex
544a5468652073697465206973206a75737420544f4f20534c4f572e204f7468657277697365
2c2077656c6c20646f6e652e81000000000000000000000020646566696e6974656c79206265
7474657220636f6d707574657220626f6f6b2073656c6563; asc TJThe site is just TOO
SLOW. Otherwise, well done............. definitely better computer book
selec;
030604 10:22:21 InnoDB: Assertion failure in thread 991475 in file
mem0pool.c line 372
"
Memory operations are protected by a mutex. As if the mutex would leak and
let other threads change the bit meanwhile.
> Regarding mem usage, the machine has 1gb, mysql is using 374MB which is
> fine as far as I am concerned. I can decrease the numbers tho, but the
> last time I did decrease the numbers you mentioned performance dropped
> and our batch jobs (not the web queries) now take about 20% longer to
> run. Do you think decreasing sort and record buffer figures might
> effect performance?
Best to test it. Note that if there is a spike of load then GROUP BY queries
can pile up and reserve lots of memory. The question is what is the memory
usage at the time of a crash.
> Thanks,
>
> Richard
Best regards,
Heikki Tuuri
Innobase Oy
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
