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
{{ message }}
Repository navigation
Delete ate.scheduler.eligible_workers from resume path #1802
Delete ate.scheduler.eligible_workers. A log at the rejection answers the question better and costs nothing on the success path.
Why
It is expensive on the resume path. The metric builds a second slice of matching workers that scheduling never reads, walks it again, and repeats the room check for each entry. That check parses resource quantity strings up to three times for each worker. The metric roughly doubles the per-worker arithmetic of a placement.
A metric cannot answer the question it was built for.#564 wanted to tell a full fleet apart from an empty constraint intersection, such as a cordoned node behind a node requirement. That needs the selector, the node requirement and the actor. substrate.yaml forbids those as metric labels and says to put them on logs and spans.
changed the title [-]Remove ate.scheduler.eligible_workers from the resume path[/-][+]Delete ate.scheduler.eligible_workers and diagnose scheduling rejections from logs[/+]on Sep 22, 2026
changed the title [-]Delete ate.scheduler.eligible_workers and diagnose scheduling rejections from logs[/-][+]Delete ate.scheduler.eligible_workers from resume path[/+]on Sep 22, 2026
Activity
JeffLuoo commentedon Sep 22, 2026
fyi - Julian Gutierrez Oschmann (@juli4n)
[-]Remove ate.scheduler.eligible_workers from the resume path[/-][+]Delete ate.scheduler.eligible_workers and diagnose scheduling rejections from logs[/+][-]Delete ate.scheduler.eligible_workers and diagnose scheduling rejections from logs[/-][+]Delete ate.scheduler.eligible_workers from resume path[/+]Delete ate.scheduler.eligible_workers (agent-substrate#1804)