You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(scheduling): return typed capacity rejection when filters drain candidates
A filter draining a non-empty candidate set produced an Internal error that
the scheduler dropped after logging, so profile handlers reported the failure
with fresh untyped errors and the director fell through to its legacy
ResourceExhausted fallback: the client got a 429 chosen by accident, with no
x-llm-d-request-dropped-reason header.
Report the drain with the same vocabulary as a flow control capacity
rejection (ResourceExhausted plus rejected-saturated), and retain per-profile
errors in Schedule, joining them into the ProcessResults error so the typed
code survives to the director's errors.As without touching any profile
handler.
The director's own pre-scheduling rejections (no endpoint candidates located,
screeners eliminating every candidate) carry rejected-no-endpoints on their
ServiceUnavailable responses, so every pre-dispatch rejection now reports a
machine-readable drop reason.
Fixesllm-d#2428
Signed-off-by: Luke Van Drie <lukevandrie@google.com>
0 commit comments