// Quota types
If we want the quota counter to start from the point when the req reaches the API, we can use rolling or flexi . If we have 6 Mps for example , the counter starts different for each Mp and use calendar so that all the Mp counters start at the same time from the start time you configure (the start time can be past date as well)
Now we know all Mps start the clock/counter at the same time .
//AsynchronousConfiguration
When we enable Asynchronous even though all the Mps start counter at the same time , Mp sync with / lookup on Cassandra will not happen at the same time .
They start 10 sec (default) from the point the policy is deployed to Mp and the deployed time can be different from Mp-Mp .
So chances that all the Mps may not go to Cassandra at the same time and you might not see expected results .
Even the connection strategy (roundrobin or leastconnection) at load balancer can add to the inconsistent behaviour of the quota.
Considering all the above factors that can change the expected behavior of quota , what is the recommended , best practice on how to use AsynchronousConfiguration ?
cc @argo any tips ?
LinkedIn
Twitter
