Follow

@mike re elasticsearch, I just found this github.com/elastic/elasticsear
Looks like by trying to give it as much RAM as possible on the server, I might have actually given it *too much*, causing the kernel to nuke it when my backups happen or other intensive tasks.

@s0 I have mine explicitly pulled back a bit.

wotwot:/etc/elasticsearch/jvm.options.d# cat wotwot.options
-Xms768m
-Xmx768m

@mike huh, just checked and I was wrong, I had mine set to 512. But had a capital M. really hope that wasn't breaking it

Sign in to participate in the conversation
Cathode Church

A place for trans makers, coders, tinkerers and dreamers.