-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
rateLimit not working as expected for long latency requests #10700
Comments
Found it can't work with the requests even the latency about tens of milliseconds. |
Hey @inforly, Thanks for the feedback, I closed the issue accordingly. |
Hello @inforly, there has been a misunderstanding I suppose. Could you provide a minimum reproducible test case? This would be very helpful. |
@jspdown yes, for example, run a http service as the following, which has long latency (1s):
Then send traffic to traefik route with rate limit, you can see the rate limit not working as expected. |
Welcome!
What did you do?
We used traefik as the ingressroute in kubernetes, the backend HTTP service needs long time to handle the requests and it can cache the requests. On average, a request takes 30s to complete.
To control the rate limit, we configured the rateLimite middleware, like 10 req/s, and we send requests as 20 req/s.
What did you see instead?
We saw traefik not working as expected, it only limited several requests, not as the one we configured.
Does traefik have different behaviors for long latency vs. short latency requests. We also tried the short latency service, like the whoami, the rateLimit work as expected.
What version of Traefik are you using?
0a79643
What is your environment & configuration?
Add more configuration information here.
If applicable, please paste the log output in DEBUG level
No response
The text was updated successfully, but these errors were encountered: