After having experience with InnoDB and MyISAM..........
There's lack in MySQL engine with InnoDB comparing to MySQL with MyISAM the problem exists when you do wrong with my.cnf configuration file for example do wrong in max_connections, table_cache Using MyISAM although with configuration key_buffer_size + (record_buffer + sort_buffer)*max_connections is greater than existing physical memory, MySQL server never crash BUT using InnoDB when you do key_buffer_size + (record_buffer + sort_buffer)*max_connections greater than memory could use by MySQL, it will crash in very heavy load for example here..... RAM 256 Mbyte, Swap 512 Mbyte with the same configuration using MyISAM, never crash, but with InnoDB .... crashed 011127 21:09:51 InnoDB: Started /usr/sbin/mysqld-max: ready for connections A mysqld process already exists at Wed Nov 28 13:45:03 EST 2001 InnoDB: Assertion failure in thread 2096211 in file trx0trx.c line 178 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] 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 agaist 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=33550336 record_buffer=131072 sort_buffer=1048568 max_used_connections=281 max_connections=400 threads_connected=159 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 493560 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 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... Stack range sanity check OK, backtrace follows: InnoDB: Thread 2051 stopped in file os0sync.c line 115 0x8078ee0 0x824829a 0x81b17d1 0x81b2284 0x80ca6e4 0x8091e31 0x808ed2e 0x8073696 0x8078bf2 0x807e197 Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/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 (nil) is invalid pointer thd->thread_id=5577 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 5577 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash Number of processes running now: 0 011128 14:40:34 mysqld restarted InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 114006046 --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
