Posted by: Peter Brawley
Date: July 02, 2017 08:49AM

> Jul 2 12:11:01 localhost kernel: Out of memory: Kill process 95362 (mysqld) score 385 or sacrifice child
> Jul 2 12:11:01 localhost kernel: Killed process 95362 (mysqld) total-vm:999223316kB, anon-rss:507787824kB, file-rss:0kB, shmem-rss:0kB

If I'm reading that correctly, MySQL crashed trying to use 1000GB memory. Estimated max MySQL RAM use is ...

innodb_buffer_pool_size + key_buffer_size + max_connections x
(read_buffer_size + read_rnd_buffer_size + sort_buffer_size + join_buffer_size)

which on the numbers you posted is 832.9GB, so the standard estimating method of max MySQL mem use gives a result that's low by 160GB, 16% of the actual value.

InnoDb buffer pool is about a tenth of what's being used, MyISAM is using much of the rest, so you'll need to cut its buffer sizes and/or cut MyISAM memory demand (eg prune/archive some data, optimise queries).

Is performance_schema off?

Are processes other than MySQL running? The error report above suggests MySQL can count on just 1TB.

What is swappiness? Is oom killer running? What does top say?

Edited 1 time(s). Last edit at 07/03/2017 11:46AM by Peter Brawley.

Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.