mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-17 15:42:24 +00:00
fix(jobs): let running jobs finish on stop, and give the worker four pg-boss sockets
Next's signal handler closed the server and called process.exit, which won the race against boss.stop, so a running job was cut off and stayed active until its expiry. The shutdown handler now holds process.exit until the boss has stopped, at most 30 s plus a margin, and compose gives the container 45 s to stop. A process that runs the worker gets four pg-boss connections instead of two for its pollers, cron, supervision and job writes; a web-only producer keeps two. Both come out of the same per-process budget.
This commit is contained in:
1 parent
27e83f1a83
commit
a20cf17539
7 files changed
+178
-26
No files matched your search
@@ -508,6 +508,11 @@ services:
|
||||
# support report and Admin > System status say so. On a busy instance,
|
||||
# raise it with APP_MEMORY_LIMIT in .env; do not lower it.
|
||||
mem_limit: "${APP_MEMORY_LIMIT:-1536m}"
|
||||
# On `docker stop` (a redeploy) the app stops taking requests, lets the
|
||||
# requests in flight finish and gives running jobs up to 30 s to end
|
||||
# before it exits. Docker's default of 10 s cut that short and left
|
||||
# jobs marked active until their expiry, holding exclusive queues.
|
||||
stop_grace_period: 45s
|
||||
healthcheck:
|
||||
test:
|
||||
[
|
||||
@@ -564,6 +569,7 @@ services:
|
||||
# max-size: "10m"
|
||||
# max-file: "3"
|
||||
# mem_limit: "${WORKER_MEMORY_LIMIT:-1536m}"
|
||||
# stop_grace_period: 45s
|
||||
|
||||
db:
|
||||
# Pinned to the concrete minor instead of the floating `16-alpine`
|
||||
|
||||
Reference in new issue
Block a user