vllm - 💡(How to fix) Fix [Bug]: MoRIIO does not support heterogenous TP [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#41211Fetched 2026-04-30 06:19:28
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
commented ×1labeled ×1

Code Example

Your output of `python collect_env.py` here
RAW_BUFFERClick to expand / collapse

Your current environment

<details> <summary>The output of <code>python collect_env.py</code></summary>
Your output of `python collect_env.py` here
</details>

🐛 Describe the bug

The MoRI-IO connector currently notifies remote ranks by iterating over its local tp size, not the remote tp size. This means if TP of the D instance != TP of the P instance, some ranks might not get notified or some notifications might go to ports that are not listened to (depending on READ or WRITE mode).

Since the connectors already sends their TP sizes in the registration messages we just have to

  1. update vllm-router to store this TP size for each instance in its service registry, and pass it along in the kv_transfer_params
  2. update the connector to iterate over the remote TP size rather than the local tp size when sending notifications

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

extent analysis

TL;DR

Update the MoRI-IO connector to iterate over the remote TP size instead of the local TP size when sending notifications.

Guidance

  • Update vllm-router to store the TP size for each instance in its service registry and pass it along in the kv_transfer_params.
  • Modify the connector to use the remote TP size for notification iteration, ensuring all ranks are correctly notified.
  • Verify the fix by testing with different TP sizes for the D and P instances to ensure notifications are sent correctly.
  • Review the registration messages to confirm that TP sizes are being sent and stored as expected.

Example

No code snippet is provided as the issue does not contain specific code references.

Notes

This fix assumes that the TP sizes are correctly sent in the registration messages and that updating the vllm-router and connector as described will resolve the notification issue.

Recommendation

Apply workaround: Update the MoRI-IO connector and vllm-router as described to ensure correct notification of remote ranks.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

vllm - 💡(How to fix) Fix [Bug]: MoRIIO does not support heterogenous TP [1 comments, 1 participants]