[MXS-173] Implement a query throttling filter Created: 2015-05-27 Updated: 2018-06-01 Resolved: 2018-05-28 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | 2.3.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | markus makela | Assignee: | Niclas Antti |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-56, MXS-SPRINT-57, MXS-SPRINT-58 |
| Description |
|
A filter which would implement and improve upon the dbfwfilter's limit_queries rule would be useful for situations where sudden traffic spikes cause a performance loss. This would also improve the quality of service by guaranteeing a consistent rate of queries to the backend instead of large spikes. The dbfwfilter's limit_queries rule is documented here: https://github.com/mariadb-corporation/MaxScale/blob/2.2/Documentation/Filters/Database-Firewall-Filter.md#limit_queries |
| Comments |
| Comment by Johan Wikman [ 2017-04-03 ] |
|
The limit_queries functionality should be removed/deprecated in the database firewall filter. All other rules just match or not a statement, which subsequently cause the statement to be either allowed or blocked depending on how the filter is configures. The limit_queries rule is not really a rule but rule and an action combined into one; it makes no sense to use limit_queries and action=allow. |