-
Notifications
You must be signed in to change notification settings - Fork 40
Fix: Set an explicit TimeoutStopSec on the Linux service unit #1079
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+16
−0
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
4f2fe9d
fix: Set an explicit TimeoutStopSec on the Linux service unit
Alan-Cha cfd0e9a
fix: Assert TimeoutStopSec's actual value, not just its presence
Alan-Cha c2aed8a
fix: Simplify the TimeoutStopSec assertion to a plain exact-value check
Alan-Cha ed0d41f
docs: Trim the TimeoutStopSec rationale comment to the core claim
Alan-Cha fc6d143
docs: Correct the TimeoutStopSec comment's framing on #1079
Alan-Cha File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion — explicit over implicit is the right call, but the comment tells only half the story and the direction is worth stating out loud.
The net effect on a stock systemd is a narrower window, not wider.
DefaultTimeoutStopSecis 90s in both the system and user managers (systemd-user.conf(5)), so this trades 90s of slack for 20s. That's still the right trade — a manager default is configurable and could just as easily be lowered under 15s, which is the real hazard — but the comment reads as if it's adding headroom when it's mostly pinning it.And 15s is the drain deadline, not the process's stop time.
shutdownCtxbounds the HTTP servers and both pipelines, butcostLedger.Close()andsessions.Close()run after that deadline with no context governing them (cmd/authbridge-proxy/main.go:987-995). So the 5s of margin here is covering unbounded post-deadline work — and per the ledger's own comment, that flush is exactly what turns "a restart loses up to 60 seconds of cost" into "an orderly stop loses nothing." A slow disk at that moment is a SIGKILL and a lost open minute.Either is fine to resolve in a sentence of comment rather than a code change; the value itself is defensible.