Skip to content

[Bugfix] Exclude numa_bind fields from ParallelConfig DP hash #41098

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
youkaichao merged 1 commit into from
Apr 28, 2026
Merged

[Bugfix] Exclude numa_bind fields from ParallelConfig DP hash #41098

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions vllm/config/parallel.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -713,6 +713,14 @@ def compute_hash(self):
"worker_extension_cls",
"_api_process_count",
"_api_process_rank",
# NUMA binding is per-rank host-side memory locality; it does
# not affect collective-communication semantics. When numa_bind
# is enabled with auto-detection, each DP rank stores its own
# NUMA node in numa_bind_nodes (see vllm/utils/numa_utils.py
# `_get_numa_node`), which would otherwise diverge the DP hash.
"numa_bind",
"numa_bind_nodes",
"numa_bind_cpus",
}

from vllm.config.utils import get_hash_factors, hash_factors
Expand Down
Loading