In order to more easily sustain the amount of requests, switch the rest-gateway's ratelimit service's backend to use the same redis as the standalone ratelimit service (same hosts but port 6380).
This will reset the rate limits (which is not an issue since we're not enforcing) and mean that future data analysis with redioscope will need to be done on that port.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| rest-gateway: Switch redis backend to 6380 instance | operations/deployment-charts | master | +19 -19 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T399291 Epic: API Rate Limiting Architecture | |||
| Open | None | T412585 Epic: Enforce API rate limits (WE5.1.3c) | |||
| Open | daniel | T398919 Epic: API rate limiting dry run (WE5.1.3b) | |||
| Resolved | Clement_Goubert | T413876 Switch ratelimit backend redis to instance 6380 |
Change #1223651 had a related patch set uploaded (by Clément Goubert; author: Clément Goubert):
[operations/deployment-charts@master] rest-gateway: Switch redis backend to 6380 instance
Change #1223651 merged by jenkins-bot:
[operations/deployment-charts@master] rest-gateway: Switch redis backend to 6380 instance