I did not know that mmap is not considered direct memory, so thanks for that. Now I can stop barking about why -XX:MaxDirectMemorySize isn't having any effect :)
-- Erik On Wed, Aug 30, 2017 at 11:39 PM, Uwe Schindler <u...@thetaphi.de> wrote: > Hi, > > As a suggestion from my side: As a first thing: disable the > bootstrap.memory_lock feature: https://www.elastic.co/guide/ > en/elasticsearch/reference/5.5/important-settings.html# > bootstrap.memory_lock > > It looks like you are using too much heap space and some plugin in your ES > installation also using the maximum direct memory size, so I have the > feeling something is using a lot direct memory and you want to limit that. > MMap is NOT direct memory! MMap is also not taken into account by the OOM > killer, because it's not owned by the process. > > To me it looks like the operating system kills your process as it sits > locked on a huge amount of memory. So disable the locking (it is IMHO > opinion not really useful and too risky). If you also have no swap disk, > then you may also try to add some swap memory and set systems's swapiness > to "10" or even lower. In production environments it is better to have a > little bit of swap as a last resort, but you should tell it with the > vm.swapiness sysctl that it should only use it as last resort. >
