[racktables-users] Re: Racktables Search crashes with Out of Memory Error Message
- From: J Lee <juleedev@xxxxxxxxx>
- To: racktables-users@xxxxxxxxxxxxx
- Date: Fri, 7 Mar 2014 08:40:44 -0500
Hi again. Just FYI. The key parameter fixed the issue was setting
join_buffer_size.
I've set it to 3M and it seems to be happy again.
There were a few other variables that I tweaked including the table cache,
and query cache. But the one that actually fixed the issue was the
join_buffer_size.
On Wed, Mar 5, 2014 at 5:02 PM, Michał Sochoń <kaszpir@xxxxxxxxx> wrote:
> First try to adjust tuning_primer.sh variables, looks like your mysql is
> overall limited in resources.
>
>
> On Wed, Mar 5, 2014 at 10:04 PM, J Lee <juleedev@xxxxxxxxx> wrote:
>
>> Hi list.
>>
>> I've run into a problem where anytime we run a search in Racktables, it
>> crashes with the following error message:
>>
>> SQLSTATE[HY000]: General error: 5 Out of memory (Needed 1216436 bytes) (
>> HY000)
>>
>> at file /var/www/localhost/htdocs/racktables/inc/database.php, line 3734
>>
>> we are running a linux server with 4GB of RAM. Nothing else is running on
>> this server except racktables/mysql.
>>
>> our mysql install is using all the out of the box settings, except today, i
>> tried changing the innodb_buffer_pool_size to increase it to 256M in an
>> attempt to resolve these errors.
>>
>> unfortunately, they're still happening.
>>
>> just wondering if anyone else has run into these types of errors in the past
>> and if so, how you resolved it?
>>
>> I'm currently reviewing the output from the script tuning_primer.sh and I
>> found the following items that may be related:
>>
>> JOINS
>> Current join_buffer_size = 132.00 K
>> You have had 965 queries where a join could not use an index properly
>> You have had 15 joins without keys that check for key usage after each row
>> You should enable "log-queries-not-using-indexes"
>> Then look for non indexed joins in the slow query log.
>> If you are unable to optimize your queries you may want to increase your
>> join_buffer_size to accommodate larger joins in one pass.
>>
>> TABLE CACHE
>> Current table_open_cache = 64 tables
>> Current table_definition_cache = 400 tables
>> You have a total of 107 tables
>> You have 64 open tables.
>> Current table_cache hit rate is 12%
>> , while 100% of your table cache is in use
>> You should probably increase your table_cache
>>
>> Any suggestions would be appreciated.
>>
>>
>
>
> --
> Michal Sochoń
> alias _KaszpiR_ kaszpir@xxxxxxxxx
> IRC: _KaszpiR_ @ freenode.net
>
Other related posts:
