Swift supports rate-limiting operations on the frontend (ms-fe) via wsgi middleware. Relevant documentation: https://docs.openstack.org/developer/swift/ratelimit.html
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| swift: add ratelimit middleware | operations/puppet | production | +12 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | fgiunchedi | T162792 Reduce Swift technical debt | |||
| Resolved | fgiunchedi | T162793 Rate limit swift operations |
Event Timeline
Comment Actions
Change 350220 had a related patch set uploaded (by Filippo Giunchedi):
[operations/puppet@production] swift: add ratelimit middleware
Comment Actions
Change 350220 merged by Filippo Giunchedi:
[operations/puppet@production] swift: add ratelimit middleware
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2017-05-09T08:05:15Z] <godog> roll-restart swift proxy for ratelimit middleware - T162793
Comment Actions
Completed, we're rate limiting non-mediawiki accounts both for container delete/create and object create/delete/update (for containers with more than 200 objects)
Swift will initially slow down clients by waiting on replies, if too much "sleep time" passes while rate-limiting clients then a HTTP 498 status will be returned instead