With the sysctl settings provided by Pete (vm.min_free_kbytes = 100
and vm.zone_reclaim_mode = 1), we've been running the linux-aws
4.4.0-1028.37 kernel successfully without an OOM killer invocation for
about four days now. Previously we would have seen three or more
occurrences of this per
Apologies - the file was inadvertently split by logrotate. I have
concatenated the entire contents of kern.log and kern.log.1 into the
attached file; these are the only kern.log files in /var/log on the
system.
I do have to redact the hostname in question, but it is a simple
substitution of
We are also experiencing this issue running linux-aws 4.4.0-1028.37,
which tracks Ubuntu kernel 4.4.0-89.112. Our use case is very similar to
comment #86
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/comments/86).
In our case ElasticSearch 2.4.5 is running under Java 1.8.0_131 with
3 matches
Mail list logo
