-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix(redis-worker): stop fair queue leaking concurrency slots #4540
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
Open
matt-aitken
wants to merge
10
commits into
main
Choose a base branch
from
fix/fair-queue-concurrency-slot-leak
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
4df6cda
fix(redis-worker): stop fair queue leaking concurrency slots
matt-aitken 35568a3
fix(redis-worker): keep metadata-derived concurrency groups on the re…
matt-aitken b2ebf18
fix(redis-worker): close the remaining concurrency slot leaks in fair…
matt-aitken c6524ca
fix(redis-worker): stop losing dead-lettered messages when the DLQ wr…
matt-aitken 3f8ed8b
fix(redis-worker,run-engine): close the remaining ways a batch item i…
matt-aitken a2f12f2
fix(redis-worker,run-engine): give the item heartbeat real margin and…
matt-aitken ff348c4
fix(run-engine,redis-worker): drop a batch item result once its lease…
matt-aitken 1b24915
docs(run-engine): state what the lease signal actually guarantees
matt-aitken 01d0666
chore(run-engine): move batch item heartbeating to its own branch
matt-aitken 72947fe
test(redis-worker): assert reclaim recovery on a stable signal
matt-aitken 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| --- | ||
| "@trigger.dev/redis-worker": patch | ||
| --- | ||
|
|
||
| Fair queue consumers no longer leak the concurrency slots that gate a tenant's throughput. Slots were held by messages that had already finished, were never reclaimed, and once enough of them accumulated every queue belonging to that tenant stopped being served. Slots are now freed on the paths that previously skipped them, freed before the record needed to recover them is discarded, and released before a reclaimed message goes back on the queue. A failed release is now surfaced instead of being silently treated as success. | ||
|
|
||
| Concurrency groups keyed on queue metadata rather than the tenant can still resolve to the wrong group when a consumer completes a message it did not enqueue, so this does not yet cover that case. | ||
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.
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.
🟡 Release note text explains internal implementation instead of user impact
The release note added for this change (
.changeset/fair-queue-concurrency-slot-leak.md:5-7) describes internal mechanics and a maintainer-facing caveat instead of one plain sentence about what changed for the user, which is what the repository requires because this text ships verbatim in user-visible release notes.Impact: Users reading the release notes get implementation detail and an internal caveat rather than a clear statement of the behaviour change.
Rule in AGENTS.md on changeset wording
AGENTS.md ("Changesets and Server Changes") states: "Write the description for users, not maintainers. Both changesets and
.server-changes/notes ship verbatim in user-visible release notes. Lead with what changed for the user - one plain sentence describing behavior, not implementation, and never naming internal tools or infra."The note instead says slots are "freed before the record needed to recover them is discarded, and released before a reclaimed message goes back on the queue. A failed release is now surfaced instead of being silently treated as success.", and the second paragraph documents a remaining internal limitation about "concurrency groups keyed on queue metadata".
Was this helpful? React with 👍 or 👎 to provide feedback.