16 Feb
2021
16 Feb
'21
8:10 a.m.
Hello,
pipelimit works only with a single instance, everything in memory, it
does not have any storage or replication. It targets to catch high
rates, like thousands of requests per seconds, in such case doing the
replication will add delays, so the measurement won't be accurate across
many nodes anyhow.
If you deal with lower rates, then you can use htable module, which has
dmq replication. You can define a hash table with the expire interval
you need for rates, then you have functions/variables to count number of
items in the hash table. Probably something like this can be implemented
with a redis server as well.
Otherwise, there is no hard limit of number of pipes for pipelimit.
Cheers,
Daniel
On 16.02.21 08:38, Daniel Donoghue wrote:
Hello,
I have 2 stateful kamailio servers that receive incoming requests, load balanced across
the 2 servers by our carrier trunk partners (outside of our control).
I am looking at putting certain invites from these trunks into pipelimit to rate limit
under some conditions but I have some questions:
1. How will pipelimit establish rates when requests can come in to either of my servers?
2. If pipelimit decides it is time to limit the requests, will both servers respect that
limit?
3. does pipelimit rely on a db or can it use dmq, redis or other methods for cross-server
communication?
4. Is there a maximum number of pipes that can be defined?
Hope somebody can help me answer these questions.
With every blessing,
—
Daniel Donoghue
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla