-
Notifications
You must be signed in to change notification settings - Fork 230
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.
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
fix: NATS queue initialization failure caused by customized served_model_name in PD disagg #354
base: main
Are you sure you want to change the base?
Conversation
…ame. Signed-off-by: Ye Cao <[email protected]>
👋 Hi dashanji! Thank you for contributing to ai-dynamo/dynamo. Just a reminder: The 🚀 |
@dashanji When is it expected to merge into the main branch? |
Please not directly choose the first element. How about we use sha256 hash or base64 encoding as stream name ? In this way we don't have to replace special characters later on? |
Refer commit bytedance-iaas@bd3f004 |
@rainj-me I think it's not a good idea to use a random one. Once we use the PD disagg in a distributed environment, how to make the P worker and D worker use the same nats stream? In this case, a customized served_model_name by users makes sense. |
sha256 is not random value |
Overview:
If we use a customized served_mode_name, the vllm will parse it as a list but not a string.
https://github.com/ai-dynamo/dynamo/blob/main/examples/llm/utils/vllm.py#L49
Thus, the NATS queue initialization will crash there as the stream_name (assigned by served_model_name) is a list.
https://github.com/ai-dynamo/dynamo/blob/main/examples/llm/utils/nats_queue.py#L42
Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)