When the PUMA_MAX_RAM environment variable is set, PumaWorkerKiller was apaprently mostly disabled: the typicall recurring message PumaWorkerKiller: Consuming 338.73828125 mb with master and 2 workers.. was not present in the log.
Converting that variable to an Integer before passing it to the PumaWorkerKiller configuration seems to fix this.
When the
PUMA_MAX_RAM
environment variable is set,PumaWorkerKiller
was apaprently mostly disabled: the typicall recurring messagePumaWorkerKiller: Consuming 338.73828125 mb with master and 2 workers..
was not present in the log.Converting that variable to an Integer before passing it to the PumaWorkerKiller configuration seems to fix this.
cc/ @Cedric-Pigeon