Rollback kills the new replica without its grace period #101
Labels
No labels
priority/P0
priority/P1
priority/P2
priority/P3
size/L
size/M
size/S
size/XL
size/XS
state/blocked
state/done
state/in-progress
state/in-review
state/needs-refinement
state/ready
type/bug
type/chore
type/feature
type/refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
amtronics/platform-actions#101
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
When a new replica never turns healthy, the rolling swap removes it with
docker rm -f: SIGKILL, with no stop signal and no grace period. An unhealthy replica still runs its background work. Rihla's api runs a welcome-email pass at startup, so a rollback that lands mid-pass kills the sends it has claimed, and those are never resent. Seen live in rihla run 891 (suhba/rihla#417); harmless that time because the pass had nothing to send.Scope
docker stop, so their stop signal andstop_grace_periodapply, then remove them.Acceptance criteria