Articles in this section

Validate enable-quotas

Context

The “enable-quotas” is a new feature since version 5.6.  How do we validate it is working?


 

Method

This new feature is not auto-throttling the transaction rate but the application will get error code 83 (AS_SEC_ERR_QUOTA_EXCEEDED) when transaction rate exceeded the quotas.   

 

If report-violation is enabled, then it will appear in the log as audit context and tsvc error also get incremented to reflect the violation.  It is easier to illustrate with an example:

INFO (info): (ticker.c:635) {test} client: tsvc (11706,0) proxy (0,0,0) read (27,0,0,6190,0) write (8403,0,0,0) delete (0,0,0,0,0) udf (0,0,0,0) lang (0,0,0,0)

INFO (audit): (security.c:7325) quota exceeded | client: <n/a> | authenticated user: user1 | action: read | detail: quota=888

INFO (audit): (security.c:7325) quota exceeded | client: <n/a> | authenticated user: user1 | action: write | detail: quota=1400

INFO (info): (ticker.c:635) {test} client: tsvc (17302,0) proxy (0,0,0) read (39,0,0,10962,0) write (13151,0,0,0) delete (0,0,0,0,0) udf (0,0,0,0) lang (0,0,0,0)


 


Applies To Earliest Version

5.6

Applies To Latest Version

Current Version
Was this article helpful?
0 out of 0 found this helpful