You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The request_id field used in the LLM Engine is assumed to be unique, but it is a parameter that can be set by the caller. After #9550, the request_id is configurable even by a caller to the OpenAI Server.
I originally encountered this issue while investigating the cause of negative metrics in #10430. I found that sending two requests concurrently with the same request id can cause the negative metric error. Example bash using curl:
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.
The text was updated successfully, but these errors were encountered:
Your current environment
The environment is not relevant.
Model Input Dumps
No response
🐛 Describe the bug
The
request_id
field used in the LLM Engine is assumed to be unique, but it is a parameter that can be set by the caller. After #9550, therequest_id
is configurable even by a caller to the OpenAI Server.I originally encountered this issue while investigating the cause of negative metrics in #10430. I found that sending two requests concurrently with the same request id can cause the negative metric error. Example bash using
curl
:The fix in #10430 properly prevents the crash, but only one request gets a response and the other connection hangs open.
Other users have reported other bad behavior that looks to be caused by duplicate request_ids:
asyncio.gather
with vllm version 0.5.5 #8393Counters can only be incremented by non-negative amounts.
: [Bug]: errorCounters can only be incremented by non-negative amounts.
inmetrics
module #6642Before submitting a new issue...
The text was updated successfully, but these errors were encountered: