Skip to content
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

[Badcase]: 抢占式实例部署qwen2.5-72B成功,调用失败 #1088

Open
4 tasks done
ZX1998-12 opened this issue Nov 18, 2024 · 2 comments
Open
4 tasks done

[Badcase]: 抢占式实例部署qwen2.5-72B成功,调用失败 #1088

ZX1998-12 opened this issue Nov 18, 2024 · 2 comments
Labels

Comments

@ZX1998-12
Copy link

Model Series

Qwen2.5

What are the models used?

qwen2.5-72B

What is the scenario where the problem happened?

抢占式实例部署qwen2.5-72B成功,调用失败

Is this badcase known and can it be solved using avaiable techniques?

  • I have followed the GitHub README.
  • I have checked the Qwen documentation and cannot find a solution there.
  • I have checked the documentation of the related framework and cannot find useful information.
  • I have searched the issues and there is not a similar one.

Information about environment

部署指令:vllm serve /home/Qwen2.5/Qwen2.5-72B-Instruct --port 6666 --host 0.0.0.0 --tensor-parallel-size 4 --served-model-name Qwen2.5-72B --enforce-eager

部署成功但是调用失败截图
lQDPKILMLK0gXBHNAeLNAtCwCCqx7-_WCbIHIQzau6d_AA_720_482

应该是和MQLLMEngine交互数据超时了,但是不知道解决办法

Description

Steps to reproduce

This happens to Qwen2.5-xB-Instruct-xxx and xxx.
The badcase can be reproduced with the following steps:

  1. ...
  2. ...

The following example input & output can be used:

system: ...
user: ...
...

Expected results

The results are expected to be ...

Attempts to fix

I have tried several ways to fix this, including:

  1. adjusting the sampling parameters, but ...
  2. prompt engineering, but ...

Anything else helpful for investigation

I find that this problem also happens to ...

@jklj077
Copy link
Collaborator

jklj077 commented Nov 19, 2024

for vllm internal errors, I advised you to raise issues at https://github.com/vllm-project/vllm/issues

Copy link

This issue has been automatically marked as inactive due to lack of recent activity. Should you believe it remains unresolved and warrants attention, kindly leave a comment on this thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants