Skip to content

fix: Pin Ray placement group bundles to allowlisted nodes during scale up#44762

Open
weizhoublue wants to merge 1 commit into
vllm-project:mainfrom
weizhoublue:fix-elastic-scale-dp-placement-node-allowlist
Open

fix: Pin Ray placement group bundles to allowlisted nodes during scale up#44762
weizhoublue wants to merge 1 commit into
vllm-project:mainfrom
weizhoublue:fix-elastic-scale-dp-placement-node-allowlist

Conversation

@weizhoublue

@weizhoublue weizhoublue commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Purpose

Root Cause
PR #44669 restricted placement groups to allowlisted nodes only during initial deployment (via create_dp_placement_groups ).
Scale-up workflow routing through utils.py ignores VLLM_RAY_DP_PLACEMENT_NODE_IPS environment variable. Furthermore, it creates Ray placement group bundles without node-specific resource constraints, allowing Ray scheduler to bypass desired layout.

Test Plan

Test Result


Essential Elements of an Effective PR Description Checklist
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.

@weizhoublue weizhoublue requested a review from njhill as a code owner June 7, 2026 05:02

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

@mergify mergify Bot added the v1 label Jun 7, 2026
@weizhoublue

weizhoublue commented Jun 7, 2026

Copy link
Copy Markdown
Contributor Author

@walterbm please help check whether this PR makes sense , thanks

@weizhoublue weizhoublue closed this Jun 7, 2026
@weizhoublue weizhoublue reopened this Jun 7, 2026
Comment thread vllm/v1/engine/utils.py
"There can only be one head node"
)

# optionally restrict DP placement to a caller-provided node set.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe this can be extracted into a helper to avoid duplication across both checks

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good. thanks
I updated it

@walterbm

walterbm commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

@walterbm please help check whether this PR makes sense , thanks

good catch! looks reasonable to me

Signed-off-by: weizhoublue <weizhou.lan@daocloud.io>
@weizhoublue weizhoublue force-pushed the fix-elastic-scale-dp-placement-node-allowlist branch from fa955a0 to 950d360 Compare June 8, 2026 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants