I have MySQL with about 12 billion rows
when i try to create 2 process, each select count(*) on the same
table.... after a long time about 30 minutes
it crashed :(
ANy information?
Log file :
051116 20:27:22InnoDB: Assertion failure in thread 2366216768 in file
srv0srv.c line 1873
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
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=402653184
read_buffer_size=12578816
max_used_connections=31
max_connections=910
threads_connected=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 1782208 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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=0x8d0992ec, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8115587
0x4004a618
(nil)
0x420de407
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 trac
e. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
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
051116 20:27:23 mysqld restarted
InnoDB: ##########################################################
InnoDB: WARNING!
InnoDB: The log sequence number in ibdata files is higher
InnoDB: than the log sequence number in the ib_logfiles! Are you sure
InnoDB: you are using the right ib_logfiles to start up the database?
InnoDB: Log sequence number in ib_logfiles is 33 1628260918, log
InnoDB: sequence numbers stamped to ibdata file headers are between
InnoDB: 0 0 and 192 460914688.
InnoDB: ##########################################################
051116 20:27:24 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
051116 20:27:24 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 33 1628260918.
InnoDB: Doing recovery: scanned up to log sequence number 33 1628260918
051116 20:27:24 InnoDB: Flushing modified pages from the buffer pool...
051116 20:27:24 InnoDB: Started; log sequence number 33 1628260918
/usr/sbin/mysqld-max: ready for connections.
Version: '4.1.9-Max' socket: '/var/lib/mysql/mysql.sock' port: 3306
Official MySQL RPM
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
