Solving OOM by Resizing MySQL’s innodb_buffer_pool_size

Several developers at one of Bytecode IO’s clients reached out for help after some of their scripts began mysteriously dying. These scripts connected to a MySQL 5.6 server the developers had configured and were doing large SQL transforms. After examining the configured innodb_buffer_pool_size, we found that it was set to 92% of RAM and the server had swap disabled.

After checking the syslog we discovered that OOM was called:
mysqld invoked oom-killer

To resolve the issue we reduced innodb_buffer_pool_size to 75% of available memory.

Leave a Reply