uptime-kuma: set restart_policy.delay to 30s
Increases the delay before Swarm restarts a failed uptime-kuma task from the default 5s to 30s. Applied live via `docker service update --restart-delay 30s` on 2026-07-26; this persists it so it survives the next stack deploy. Note: this does not pin the task to a specific node or prevent cross-node reschedule races against the CephFS-backed SQLite data dir - it only slows the restart-after-failure loop. See prior incident notes for the DB corruption root cause discussion.
This commit is contained in:
@@ -66,6 +66,8 @@ services:
|
|||||||
max-size: "10m"
|
max-size: "10m"
|
||||||
max-file: "3"
|
max-file: "3"
|
||||||
deploy:
|
deploy:
|
||||||
|
restart_policy:
|
||||||
|
delay: 30s
|
||||||
labels:
|
labels:
|
||||||
- traefik.enable=true
|
- traefik.enable=true
|
||||||
- traefik.http.routers.uptime.rule=Host(`uptime.${DOMAIN}`)
|
- traefik.http.routers.uptime.rule=Host(`uptime.${DOMAIN}`)
|
||||||
|
|||||||
Reference in New Issue
Block a user