Skip to content

Conversation

@KuntaiDu
Copy link
Collaborator

@KuntaiDu KuntaiDu commented Oct 27, 2025

Due to #25712 , currently vLLM will hard fail if the user simply set a connector because vLM enables HMA by default.

To avoid hard fail, before discussing with @njhill to figure out a better solution, let's just turn off HMA when a connector is being set.


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.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

@mergify
Copy link

mergify bot commented Oct 27, 2025

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @KuntaiDu.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify bot added the needs-rebase label Oct 27, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request aims to fix a stability issue by disabling the Hybrid Memory Allocator (HMA) when a connector is configured. While the change is functionally correct in its intent, it introduces a redundant code block. The check for kv_transfer_config is now performed twice consecutively. This should be consolidated into a single check to improve code clarity and maintainability.

@mergify mergify bot removed the needs-rebase label Oct 27, 2025
@KuntaiDu
Copy link
Collaborator Author

Code Review

This pull request aims to fix a stability issue by disabling the Hybrid Memory Allocator (HMA) when a connector is configured. While the change is functionally correct in its intent, it introduces a redundant code block. The check for kv_transfer_config is now performed twice consecutively. This should be consolidated into a single check to improve code clarity and maintainability.

It's now fixed. Thanks for the reminder.

Copy link
Collaborator

@NickLucche NickLucche left a comment

Choose a reason for hiding this comment

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

Fixes

(EngineCore_DP0 pid=3595930) ValueError: Connector NixlConnector does not support HMA but HMA is enabled. Please set `--disable-hybrid-kv-cache-manager`.

I think we should just change logic to disabling it if it does not support hma with the interface you defined, given it's on by default

Copy link
Member

@njhill njhill left a comment

Choose a reason for hiding this comment

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

Thanks @KuntaiDu

@njhill njhill added this to the v0.11.1 milestone Oct 27, 2025
Signed-off-by: KuntaiDu <[email protected]>
@KuntaiDu KuntaiDu requested a review from njhill October 27, 2025 18:21
@KuntaiDu
Copy link
Collaborator Author

Fixes

(EngineCore_DP0 pid=3595930) ValueError: Connector NixlConnector does not support HMA but HMA is enabled. Please set `--disable-hybrid-kv-cache-manager`.

I think we should just change logic to disabling it if it does not support hma with the interface you defined, given it's on by default

Agree. For now let's temporarily disable it for all connectors to avoid blocking the release. Will figure out a way to only turn off HMA when connector does not support it.

Copy link
Member

@njhill njhill left a comment

Choose a reason for hiding this comment

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

Thanks @KuntaiDu

@njhill njhill added the ready ONLY add when PR is ready to merge/full CI is needed label Oct 27, 2025
@njhill njhill enabled auto-merge (squash) October 27, 2025 18:47
Copy link
Collaborator

@ApostaC ApostaC left a comment

Choose a reason for hiding this comment

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

LGTM!

@simon-mo
Copy link
Collaborator

Ready to be force merged?

@simon-mo simon-mo disabled auto-merge October 28, 2025 01:32
@simon-mo simon-mo merged commit 255e34c into vllm-project:main Oct 28, 2025
42 of 45 checks passed
@KuntaiDu
Copy link
Collaborator Author

Ready to be force merged?

Yes and ty for the force merge.

@KuntaiDu KuntaiDu deleted the kuntai-disable-HMA-for-connector-for-now branch October 29, 2025 04:31
ilmarkov pushed a commit to neuralmagic/vllm that referenced this pull request Nov 7, 2025
ZhengHongming888 pushed a commit to ZhengHongming888/vllm that referenced this pull request Nov 8, 2025
rtourgeman pushed a commit to rtourgeman/vllm that referenced this pull request Nov 10, 2025
devpatelio pushed a commit to SumanthRH/vllm that referenced this pull request Nov 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready ONLY add when PR is ready to merge/full CI is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants