Repository navigation
Admin API: list connected workers and queued demand - #2804
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
amankrx
force-pushed
the
pr/admin-listings
branch
from
September 28, 2026 11:29
7b61fc5 to
c8c6850
Compare
amankrx
force-pushed
the
pr/admin-listings
branch
from
September 28, 2026 11:30
c8c6850 to
a82b3b4
Compare
(cherry picked from commit 2dae64b02ffd7d029cd26fed6abe626a41e2980d)
(cherry picked from commit db786d898d7a9401e40ca90f1427a41e02411e37)
(cherry picked from commit 2af91b8a660b01d9ff7b1a50ab2d750fdd597ea4)
(cherry picked from commit b63338ef1bc526078ef96ce6cb79d777012cbb0c)
amankrx
force-pushed
the
pr/admin-listings
branch
from
September 28, 2026 11:34
a82b3b4 to
503b809
Compare
amankrx
force-pushed
the
pr/admin-listings
branch
from
September 28, 2026 18:38
9ad2d22 to
70fc569
Compare
amankrx
force-pushed
the
pr/admin-listings
branch
from
September 28, 2026 18:48
70fc569 to
7af0ba9
Compare
MarcusSorealheis
approved these changes
Sep 28, 2026
MarcusSorealheis
left a comment
Member
There was a problem hiding this comment.
LGTM thank you for this one also
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What and why
The admin listener gains two read-only listings: the workers connected to this scheduler with their properties and running actions, and the queued demand with each action's properties and the client's last keepalive. The demand listing reads the queue the way the matcher does, so it sees what the matcher sees. This is what a provisioner should scale on instead of reading the scheduler's Redis directly.
How was this verified?
admin_test.rs: the demand listing returns queued actions highest priority first with their properties, queue time and the client's last keepalive; an action a worker is running leaves the demand and shows on that worker with the room it took; both listings round-trip through the JSON the endpoint serves. A fixed listing covers what happens between the filter and the read: a record that was dispatched, expired or cannot be decoded is left out and counted, and a store failure fails the listing; both fail without the change. On a test cluster the provisioner's counts from the admin API matched the matcher's queue depth metric while the Redis-derived counts drifted during evictions.Risk
Low. New read-only endpoints on the admin listener, which is off unless configured. No config, wire or data changes elsewhere.
AI assistance
An agent drafted the change and I reviewed every line.
This change is