Rick James,
Thank you very much for your response and suggestions. I'll change the parameters based on your recommendations and start the server with new configuration. I'll let you know the result.
*****
*****Perhaps this should have underscores, not dashes?
*****open-files-limit = 16384
*****Do SHOW VARIABLES LIKE 'open%';
*****to see what value it got.
*****
Ya..You are right. It shows "32768".
*****
*****This is wrong:
*****key_buffer_size = 12GB
*****Even in a 64-bit OS, it is limited to 4GB. I suspect you got the bottom 32 *****bits, namely 0 bytes. Suggest 4000M, instead.
*****
I am using 64 bit OS. I already read in the following link that the MySQL 5.0.52 or latest is allowed larger than 4 GB. However, I tried to set the value and check it using 'show variables like 'key_buffer_size'' and it displays properly. That's why I increased it to 12 GB. As per your suggestion, I'll change it to 4000M.
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_key_buffer_size
*****This is not a good idea:
*****query_cache_size = 2GB
*****There are inefficiencies in the handling of the Query Cache such that this *****size might actually slow down the system. Suggest more like 100M.
*****Given that you have 32GB of RAM and only 24MB of InnoDB tables, may as well *****give it the room it needs:
*****innodb_log_buffer_size = 30M -- not a mere 1M
I'll change the above variables as per your suggestion.
*****What is in mysqld.err ?
091021 8:31:18 InnoDB: Started; log sequence number 0 2590054257
091021 8:31:20 [Note] /home/sas/mysql/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
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=12884901888
read_buffer_size=33550336
max_used_connections=14
max_connections=50
threads_connected=10
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 15859511 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x2aac44082c60
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=0x4518d068, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
(nil)
Stack trace seems successful - bottom reached
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 0x1080d0d0 = INSERT INTO `PT_ST_diskstats_partition_R` (`NODEID`,`STATSID`,`TIMESTAMP`,`NAME`,`DRIVE`,`READ`,`READ_SECTOR`,`WRITE`,`WRITE_SECTOR`) VALUES (29,1009,1256173528000,'/dev/sda1','sda',0,0,10,80)
thd->thread_id=82
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
091021 18:07:34 mysqld restarted
091021 18:07:34 [Warning] One can only use the --user switch if running as root
091021 18:07:34 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...
091021 18:07:34 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 2619883563.
InnoDB: Doing recovery: scanned up to log sequence number 0 2619888982
091021 18:07:34 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
091021 18:07:34 InnoDB: Started; log sequence number 0 2619888982
091021 18:07:36 [Note] /home/sas/mysql/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
Edited 1 time(s). Last edit at 10/22/2009 12:25AM by Ramesh Kumar.