Solved: How to use Reset Quota correctly? - Page 2

sidd-harth · 07-01-2016 02:24 AM

I am using a quota policy as below, 10 request per week,

<Quota  name="Quota-1" type="flexi">
    <DisplayName>Quota-1</DisplayName>
    <Properties/>
    <Distributed>true</Distributed>
    <Synchronous>true</Synchronous>
    <Identifier ref="request.queryparam.apikey"/>
    <Allow countRef="verifyapikey.Verify-API-Key-1.apiproduct.developer.quota.limit"/>
    <Interval ref="verifyapikey.Verify-API-Key-1.apiproduct.developer.quota.interval"/>
    <TimeUnit ref="verifyapikey.Verify-API-Key-1.apiproduct.developer.quota.timeunit"/>
</Quota>

Now I have reached the limit. So I want to use Reset quota,

<ResetQuota name="Reset-Quota-1">
    <DisplayName>Reset Quota-1</DisplayName>
    <Properties/>
    <Quota name="Quota-1">
        <Identifier ref="request.queryparam.apikey">
            <Allow>10</Allow>
        </Identifier>
    </Quota>
</ResetQuota>

So this should ideally allow 10 more requests based on identifier right?

But in trace it shows this,

My requirement is when quota(10 request per week) is completed I want to reset it again to 10 requests per week.

How can I do this?

anilsr

@Barahalikar Siddharth , Great Question.

If you place the reset quota after quota policy in request / response flow,
- It will never execute / keep increasing quota of the request so that quota will never end.
- It will never execute because flow will be changed to error flow & reset quota will never execute
- It will keep increasing quota & quota will never end because reset quota actually works as increase quota / tempIncreaseQuota. For more detail see link here.
If you place the reset quota before quota policy in request / response flow,
- It will keep increasing quota of the request so that quota will never end until unless you conditionally execute reset quota to increase quota

Ideally, I think, You should place reset quota policy in fault rules with a specific condition match to reset quota.

The ResetQuota policy should really be called "IncreaseQuota" or "TempIncreaseQuota" because the way it works is:

- Add a value to available.count

- Subtract that same value from used.count

Those changes disappear when the Quota policy next resets!

View solution in original post