cxserver service should use rate-limiter feature available from service-runner. It should help to prevent cases like T210485.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | santhosh | T210581 Use rate-limiter for cxserver | |||
Declined | None | T212417 cxserver: Set default config options in app.js |
Event Timeline
Change 476233 had a related patch set uploaded (by Santhosh; owner: Santhosh):
[mediawiki/services/cxserver@master] Introduce rate limiting
Change 476233 merged by jenkins-bot:
[mediawiki/services/cxserver@master] Introduce rate limiting
Patch comes with a default config. Do we need to set anything in production config when deploying it?
Change 480939 had a related patch set uploaded (by Santhosh; owner: Santhosh):
[mediawiki/services/cxserver@master] Move the ratelimiter rate and key options to service configuration
Change 480945 had a related patch set uploaded (by KartikMistry; owner: KartikMistry):
[mediawiki/services/cxserver/deploy@master] ratelimite: Update config for key and rate
Change 480939 merged by jenkins-bot:
[mediawiki/services/cxserver@master] Move the ratelimiter rate and key options to service configuration
Change 480945 merged by jenkins-bot:
[mediawiki/services/cxserver/deploy@master] ratelimite: Update config for key and rate
Mentioned in SAL (#wikimedia-operations) [2018-12-20T12:43:33Z] <kartik@deploy1001> Started deploy [cxserver/deploy@16f65cb]: Update cxserver to 803baa4 (T210581, T211889, T144467, T209473)
Mentioned in SAL (#wikimedia-operations) [2018-12-20T12:48:15Z] <kartik@deploy1001> Finished deploy [cxserver/deploy@16f65cb]: Update cxserver to 803baa4 (T210581, T211889, T144467, T209473) (duration: 04m 42s)