Bug #46382 | MySQL reports running out of memory | ||
---|---|---|---|
Submitted: | 25 Jul 2009 7:33 | Modified: | 27 Aug 2009 7:46 |
Reporter: | Database Administrator | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.1.35 | OS: | Other (Centos 5) |
Assigned to: | CPU Architecture: | Any | |
Tags: | MySQL 5.1.35 |
[25 Jul 2009 7:33]
Database Administrator
[25 Jul 2009 7:42]
Database Administrator
Content of My.cnf
Attachment: my.txt (text/plain), 4.19 KiB.
[25 Jul 2009 8:04]
Valeriy Kravchuk
Thank you for the problem report. Please, send the results of: uname -a from your system. I want ot check if you run 32-bit OS.
[25 Jul 2009 8:35]
Database Administrator
Dear Valeriy Kravchuk, Thanks for your prompt reply.Please find the output of uname -a uname -a Linux dbloans.gnsaindia.com 2.6.18-8.el5 #1 SMP Thu Mar 15 19:57:35 EDT 2007 i686 i686 i386 GNU/Linux
[25 Jul 2009 9:17]
Valeriy Kravchuk
So this is 32-bit Linux... Please, try to set innodb_buffer_pool_size = 1800M in my.cnf and start your server again. You can not get continuous memory allocation of 2+ G on 32-bit Linux.
[27 Jul 2009 7:35]
Database Administrator
Hi Valeriy Kravchuk, Thanks for your reply. I have managed to make the database online by changing the configuration file shipped with the MySQL rpm package. I have attached that config file. Also innodb_buffer_pool_size is set a 2GB in that file and the server is running for nearly 3 days without reporting out of memory. These are all the notable changes made in first my.cnf file while the server reports out of memory. innodb_data_file_path = ibdata1:50M:autoextend innodb_file_per_table=1 innodb_open_files=600 Are the above parameters can be considered as suspect?
[27 Jul 2009 7:35]
Database Administrator
Present My.cnf
Attachment: New My.txt (text/plain), 20.06 KiB.
[27 Jul 2009 7:46]
Valeriy Kravchuk
This one: innodb_file_per_table=1 may lead to increased internal InnoDB's "data dictionary" in memory maybe if you have a lot of InnoDB tables. But with this being set and innodb_buffer_pool_size=1800M you should be safe enough anyway. Please, check.
[27 Aug 2009 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".