Bug #29544 Partition table crashed
Submitted: 4 Jul 2007 10:12 Modified: 4 Aug 2007 10:55
Reporter: Lim tienaik Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Partitions Severity:S2 (Serious)
Version:5.1.19-beta-log OS:Linux
Assigned to: CPU Architecture:Any
Tags: ALTER TABLE, out of memory

[4 Jul 2007 10:12] Lim tienaik
Description:
trying to partition a table into about 800 partitions, but it failed with out of memory as well as crashed the server.

I am working on a 4Core 4gb memory 1tb hdd server, so the server should be able to fit in more data than shown.

070704 17:41:29 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 57688 bytes)
070704 17:41:29 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
070704 17:41:29 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 184960 bytes)
070704 17:41:29 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
070704 17:41:29 - 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=536870912
read_buffer_size=20967424
max_used_connections=11
max_threads=151
threads_connected=7
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2515169 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x8fb16760
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x8fd549dc, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81e4a57
0x834f755
0x834c00a
0x8241397
0x823f9b7
0x82ee155
0x82eee7c
0x8220a03
0x8220ce8
0x81f52d9
0x81f04dd
0x81f6a95
0x81eddb3
0x81ed90e
0x81ec94a
0x7a4341
0x9ca6fe
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xb644858 = SHOW STATUS
thd->thread_id=430
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
070704 17:41:30  mysqld restarted

How to repeat:
alter myisam table having 30mil rows
[4 Jul 2007 10:55] Sveta Smirnova
Thank you for the report.

There is "SHOW STATUS" statement in the error log. Please check if your case is duplicate of bug #28488
[4 Jul 2007 10:56] Sveta Smirnova
See also Bug #28487 and Bug #28489
[4 Aug 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".