Systemd kills drip daemon and standby vm

(Robert R) #1


Just noticed in my development setup that setting USEDRIP doesn't improve the logstash start time when running logstash as a systemd service.

Looking more closely what I notice is that 3 PIDs are completely different between service restarts. What I see is the PIDs for the active JVM, the drip daemon and the standby JVM.

Even if I just kill the active JVM directly with the kill command, systemd kicks in and kills the other two and starts drip again from scratch!

I think this may be an exotic, and unsupported usecase but I would be curious to see if you have any suggestions as to how I might address this?


(system) #2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.