Comments (1)
I see that you updated your comment and it originally had rate=0.5
and that would have likely been the culprit since that's one new request every 2 seconds.
Your current comment's settings are max=1
(burst limit), rate=0.1
(1 leak every 10s), and duration=10
(minutes).
- If you made a request at T0 then made a request at T1-9 you should have exceeded your burst limit of
max=1
. - If you made a request at T10 then you should have been able to make another request.
- Your timeout
duration=10
should mean that after 10 minutes normal behavior should continue again. - Depending on which caching driver you're using
cache:clear
might not do anything but that is how you'd clear it if you were usingfile
driver.
It's hard to know for sure what's going on in your particular case, also because your burst rate is quite small. Most use cases I've seen where the desired value is small, it's set to something like 3 and in a space of 30 seconds (based on your rate=0.1
) of idle requests, the user's full max=3
requests should be available again. In the odd case that there's a race condition, you won't hit the quota by accident.
The User
resolver uses IP addresses when the user is not authenticated and that can lead to shared IPs causing all users to be blocked, especially if using a load balancer where the load balancer's IP is what's being used instead of the X-Requestor-IP address. You may have to create a custom resolver for your application's unique situation.
If you can provide a specific repo I can install that's all configured and has the NodeJS tester in it then I might be able to figure out if there's a problem with the rate limiter or something else going on.
from ratelimiter.
Related Issues (11)
- Logo Design HOT 1
- Cache record expiration time is erroneously passed as a float HOT 1
- User-Resolver: sha1() expects parameter 1 to be string, int given HOT 1
- Setting 24 hour rate limit HOT 1
- Configuring a global & route limit HOT 2
- Possible to tag a release? HOT 5
- redis's reference implementation "Sliding Window Rate Limiting" HOT 8
- Setting limits that aren't per second HOT 2
- Timeout TTL set incorrectly HOT 2
- Hit TTL potentially set incorrectly... HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ratelimiter.