On Wed, Jun 10, 2009 at 08:00:42AM +0100, Gaby Vanhegan wrote:
> On 9 Jun 2009, at 22:43, Daniel Ouellet wrote:
>
>> If I may asked, why would you really want to get a 2GB buffer?
>
> The app generates a lot of database traffic, as well as doing some
> fairly large transactional queries, hence the need for InnoDB. MySQL
> queries keep failing with lack of memory errors:
>
> 090609 17:23:42 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed
> 1048548 bytes)
> 090609 17:25:10 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed
> 260160 bytes)
> 090609 17:25:11 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed
> 260160 bytes)
> 090609 17:25:11 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed
> 260160 bytes)
> 090609 17:25:11 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed
> 260208 bytes)
> 090609 17:25:11 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed
> 1048548 bytes)
> 090609 17:25:23 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed
> 260464 bytes)
>
> And bouncing the MySQL server seems to bring it back to life. If I
> can't change the hard limits on the OS, is there something I can do to
> MySQL to make it happier?
Allocate less space to the various innodb buffers so more remains for
other work.
-Otto