The OOM killer is a Linux feature designed to prevent one program monopolising
the system. I've never seen it hitting Fuseki before but have seen it hit
other database processes in the past because in-memory/aggressively cached
databases like Fuseki do tend to be large memory consumers.
See
More info:
latest Fuseki query returned 200 so no error there.
Apr 10 15:54:29 -- kernel: curl invoked oom-killer: gfp_mask=0x24201ca,
order=0, oom_score_adj=0
Apr 10 15:54:29 -- kernel: curl cpuset=/ mems_allowed=0
Apr 10 15:54:29 -- kernel: CPU: 2 PID: 26434 Comm: curl Not tainted
We still have this issue:
Apr 10 15:54:29 -- kernel: Out of memory: Kill process 17136 (java)
score 770 or sacrifice child
Apr 10 15:54:29 -- kernel: Killed process 17136 (java)
total-vm:9760620kB, anon-rss:3536204kB, file-rss:0kB
Apr 10 15:54:29 -- systemd[1]: apache-jena-fuseki.service:
