Rate limit not resetting on time

[ak-notify]

Hi,

I have rate limit configured at two levels
a. Server level - default
b. Route level - for some routes

For routes with configured rate limit (E.g 100req/min), when a constant load (requests/min more than configured limit) is applied the APIs continue to throw 429 even when the time limit for last window is expired.

Test case:
route: /test
rate limit: 100req/min
Applied load: 150req/min

Expected behaviour:
0-1min:
success: 100 req
fail: 50 req

1-2min:
success: 100 req
fail: 50 req

2-3min:
success: 100req
fail: 50 req

Total: 450req
success: 300req
fail: 150req

Actual behaviour:
0-1min:
success: 100req
fail: 50req

1-2min:
success: 0 req
fail: 150 req

2-3min:
success: 0 req
fail: 150 req

Total: 450req
success: 100req
fail: 350req

[marcuspoehls]

@ak-notify Hey Ashish, I would have the same assumptions as you. A request hitting the rate limit should not count as a request counting to the limit. A request hitting rate limit should also not continue to keep the limit window.

Feels like something is not working as expected. Did you ensure the requests per second were correct and not over the expected limit?

[ak-notify]

Yup, I'm quite certain on the number of requests/sec.
Also I verified this behaviour with another test, if there is a gap in between the load applied then the limit window resets as expected.