fix(systemd): backstop viperblock stop at 30s instead of the 90s default (#619)

In-use nbdkit children are SIGTERMed with this cgroup and run the plugin's
shutdown drain. That drain is now bounded at 20s in the plugin itself, so
30s here lets the plugin's own bound fire first and keeps SIGKILL
exceptional. At the 90s default a slow or unreachable backend stalled the
whole target-stop transaction.
This commit is contained in:
Josh Siviour
2026-07-31 23:09:19 +10:00
committed by GitHub
parent d9fb17155f
commit 70dda56fc3
@@ -15,6 +15,11 @@ ExecStart=/usr/local/bin/spx service viperblock start
Restart=on-failure
RestartSec=5
OOMScoreAdjust=-500
# Backstop for the in-use nbdkit children SIGTERMed with this cgroup. Their
# plugin bounds its own shutdown drain at 20s, so 30s lets that fire first and
# keeps SIGKILL exceptional; the 90s default let a slow backend stall the whole
# target-stop transaction.
TimeoutStopSec=30
EnvironmentFile=/etc/spinifex/systemd.env
Environment=SPINIFEX_CONFIG_PATH=/etc/spinifex/spinifex.toml
Environment=SPINIFEX_BASE_DIR=/var/lib/spinifex/viperblock/