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
[serve] Log rejected requests at router side (#51346)
## Why are these changes needed?
Router side logs (made less alarming, made clear that request will be
retried):
```
INFO 2025-03-13 13:42:35,298 serve 40047 -- Replica(id='7mqhdb0d', deployment='Model', app='default') rejected request because it is at max capacity of 1 ongoing requests. Retrying request 4a843e03-e1c7-47a2-be9d-6c0224108f42.
INFO 2025-03-13 13:42:35,298 serve 40047 -- Replica(id='7mqhdb0d', deployment='Model', app='default') rejected request because it is at max capacity of 1 ongoing requests. Retrying request 57d94c8a-13b4-4ea2-a628-75d566ef29e5.
INFO 2025-03-13 13:42:35,301 serve 40047 -- Replica(id='7mqhdb0d', deployment='Model', app='default') rejected request because it is at max capacity of 1 ongoing requests. Retrying request 4a843e03-e1c7-47a2-be9d-6c0224108f42.
```
Replica side logs about rejected requests are now DEBUG logs only.
This is to make the logs appear less alarming for users who are not
familiar with the request lifecycle. The way the logs are now, the user
can get confused reading the replica-side logs and think requests got
dropped.
https://anyscale1.atlassian.net/browse/SERVE-659
---------
Signed-off-by: Cindy Zhang <[email protected]>
0 commit comments