| Bug #65473 | Random crashes on MYSQL server | ||
|---|---|---|---|
| Submitted: | 31 May 2012 14:21 | Modified: | 30 Jun 2012 15:01 |
| Reporter: | Arnold Human | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Errors | Severity: | S1 (Critical) |
| Version: | Ver 14.14 Distrib 5.5.9 | OS: | Linux (Red Hat Enterprise Linux Server release 5.3 (Tikanga) x86_64) |
| Assigned to: | CPU Architecture: | Any | |
[31 May 2012 14:21]
Arnold Human
[31 May 2012 14:21]
Arnold Human
Our my.cnf looks like: [mysqld] datadir=/mysql1/mysql/data max_allowed_packet=50M log-bin=o9902-cordys-rep server-id=1 sync_binlog=1 binlog_format=MIXED max_connections=1024 max_user_connections=1024 innodb_file_per_table=1 ## SET BY AFH 2012-05-24 thread_concurrency=8 # Higher values does not make a difference innodb_buffer_pool_size=8G # for dedicated server set it to 80% of your RAM innodb_log_file_size=1G # set it to 25% of innodb_buffer_pool_size innodb_flush_log_at_trx_commit=0 # When you want true ACID set it to 1, but slows mysql down with factor 2. innodb_thread_concurrency=64 # do not set it higher because of thread thrashing innodb_commit_concurrency=0 # total concurrent max_heap_table_size=128M tmp_table_size=128M # Set the SQL mode to strict sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" default-storage-engine=INNODB # Query cache is used to cache SELECT results and later return them # without actual executing the same query once again. Having the query # cache enabled may result in significant speed improvements, if your # have a lot of identical queries and rarely changing tables. See the # "Qcache_lowmem_prunes" status variable to check if the current value # is high enough for your load. # Note: In case your tables change very often or if your queries are # textually different every time, the query cache may result in a # slowdown instead of a performance improvement. query_cache_size=29M # The number of open tables for all threads. Increasing this value # increases the number of file descriptors that mysqld requires. # Therefore you have to make sure to set the amount of open files # allowed to at least 4096 in the variable "open-files-limit" in # section [mysqld_safe] table_cache=500 # Maximum size for internal (in-memory) temporary tables. If a table # grows larger than this value, it is automatically converted to disk # based table This limitation is for a single table. There can be many # of them. #tmp_table_size=33M # How many threads we should keep in a cache for reuse. When a client # disconnects, the client's threads are put in the cache if there aren't # more than thread_cache_size threads from before. This greatly reduces # the amount of thread creations needed if you have a lot of new # connections. (Normally this doesn't give a notable performance # improvement if you have a good thread implementation.) thread_cache_size=11 #*** INNODB Specific options *** # Use this option if you have a MySQL server with InnoDB support enabled # but you do not plan to use it. This will save memory and disk space # and speed up some things. #skip-innodb # Additional memory pool that is used by InnoDB to store metadata # information. If InnoDB requires more memory for this purpose it will # start to allocate it from the OS. As this is fast enough on most # recent operating systems, you normally do not need to change this # value. SHOW INNODB STATUS will display the current amount used. innodb_additional_mem_pool_size=2M # If set to 1, InnoDB will flush (fsync) the transaction logs to the # disk at each commit, which offers full ACID behavior. If you are # willing to compromise this safety, and you are running small # transactions, you may set this to 0 or 2 to reduce disk I/O to the # logs. Value 0 means that the log is only written to the log file and # the log file flushed to disk approximately once per second. Value 2 # means the log is written to the log file at each commit, but the log # file is only flushed to disk approximately once per second. #innodb_flush_log_at_trx_commit=1 # The size of the buffer InnoDB uses for buffering log data. As soon as # it is full, InnoDB will have to flush it to disk. As it is flushed # once per second anyway, it does not make sense to have it very large # (even with long transactions). innodb_log_buffer_size=1M # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and # row data. The bigger you set this the less disk I/O is needed to # access data in tables. On a dedicated database server you may set this # parameter up to 80% of the machine physical memory size. Do not set it # too large, though, because competition of the physical memory may # cause paging in the operating system. Note that on 32bit systems you # might be limited to 2-3.5G of user level memory per process, so do not # set it too high. #innodb_buffer_pool_size=85M # Size of each log file in a log group. You should set the combined size # of log files to about 25%-100% of your buffer pool size to avoid # unneeded buffer pool flush activity on log file overwrite. However, # note that a larger logfile size will increase the time needed for the # recovery process. #innodb_log_file_size=17M # Number of threads allowed inside the InnoDB kernel. The optimal value # depends highly on the application, hardware as well as the OS # scheduler properties. A too high value may lead to thread thrashing. #innodb_thread_concurrency=18
[31 May 2012 15:01]
Valeriy Kravchuk
Try to decrease these values in my.cnf: max_heap_table_size=16M # was 128M tmp_table_size=16M # was 128M and check if this will change anything. If you really have up to 1000 concurrent connections and they use internal temporary tables a lot, then out of memory situation is quite possible. If this will not help and you feel the reason is some bug in MySQL, please, upgrade to recent version, 5.5.25, first (as we do not fix bugs that are not repeatable in current versions).
[1 Jun 2012 8:58]
MySQL Verification Team
Hi! This looks like a duplicate of: http://bugs.mysql.com/bug.php?id=56115 Bug 11763413: 56115: SELECT DOESN'T WORK IN PREPARED STATEMENTS WITH CURSOR PROTOCOL btw, 5.5.25 is the current version of mysql.
[1 Jul 2012 1: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".
