Rate Limit Cluster Properties

These properties configure the limits in the .   
gateway83
These properties configure the limits in the Apply Rate Limit Assertion.   
 
Property
 
 
Description
 
 
ratelimit.cleanerPeriod
 
Time for removing rate limit counters that have not been used recently. The node counters are created in the Apply Rate Limit assertion. Purging unused node counters frees up memory on the 
Layer7 API Gateway
. Allow up to a minute for changes to apply.
Default: 
13613 
(milliseconds)
 This setting must be greater than the 'Blackout' setting in the Apply Rate Limit Assertion, if used. Otherwise, the cleaner will run before the blackout period completes, which resets the rate limiters and causes the Apply Rate Limit Assertion to behave unexpectedly.
 
ratelimit.clusterPollInterval
 
Time between checks of the cluster status table, to see how many cluster nodes are up.
Default: 
43000 
(milliseconds)
 
ratelimit.clusterStatusInterval
 
Maximum time since the last posting for a node to be considered "up."  A cluster node posts its status periodically to indicate that it is operational.
Default: 
8000 
(milliseconds)
 
ratelimit.maxNapTime
 
Maximum time a request (subject to traffic shaping) waits before checking its status.
Default: 
4703 
(milliseconds)
 
ratelimit.maxQueuedThreads
 
Maximum number of threads permitted to be queued in a node. Used to delay requests for the Apply Rate Limit assertion.
Default: 
70
 
 
ratelimit.maxTotalSleepTime
 
Maximum time a request subject to traffic shaping waits before failing.
Default: 
18371 
(milliseconds)