fix(configs): pin head unschedulable — ray-data (batch 3)#910
Merged
Conversation
Contributor
Author
|
/test-template unstructured_data_ingestion vhol-ray-data audio-dataset-curation-llm-judge |
Contributor
Author
|
/test-template e2e-timeseries-forecasting |
These configs have worker groups or auto_select, so at launch the head is a coordinator, not a work node. Set head_node.resources CPU: 0 in aws.yaml and gce.yaml so the repo config equals what ships to S3 — the build-time compute-config conversion injects head resources when the field is absent, the silent drift behind the head-vs-worker framework skew. Heads are CPU-only instances, so CPU: 0 alone makes them unschedulable (no GPU to pin). Templates: unstructured_data_ingestion, vhol-ray-data, audio-dataset-curation-llm-judge, e2e-timeseries-forecasting https://claude.ai/code/session_01QmLc4yWtmC3PX2NwWzPbzD Signed-off-by: Aydin Abiar <aydin@anyscale.com>
Aydin-ab
force-pushed
the
fix/batch-3-head-pin-deps
branch
from
July 20, 2026 22:50
e95a959 to
e7e03a3
Compare
elliot-barn
approved these changes
Jul 22, 2026
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
2 participants
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.
Pins the head node unschedulable (
resources: {CPU: 0}) in the aws + gce compute configs. These configs have worker groups or auto_select, so the head is a coordinator, not a work node: the launch-time conversion injects this when the field is absent, so setting it explicitly makes the repo config equal what ships to S3 (andrayapp testreproduces the real worker placement instead of co-locating on a schedulable head). Heads are CPU-only instances, soCPU: 0alone is unschedulable. Config-only.Templates: unstructured_data_ingestion, vhol-ray-data, audio-dataset-curation-llm-judge, e2e-timeseries-forecasting
Testing
Validated green via
/test-template(Buildkite). The earlierCPU: 0, GPU: 0→CPU: 0normalization is a no-op on CPU-only heads (identical Ray resources), so not re-tested.Part of the head-unschedulable sweep; a companion check (#924) enforces this policy repo-wide.
https://claude.ai/code/session_01QmLc4yWtmC3PX2NwWzPbzD