2023-05-17: RedisCache Client error
Customer Impact
We saw client_connection
saturating on redis-cache
which ends up affecting web
and api
services, this affected 1% of requests in web
and 2% in api
in a 20min window where we send 5xx errors to our users. To prevent saturation we've increased the maxclients
from 40k to 60k (50% increase). However, @reprazent did see an increase in redis_connected_clients
that started on 2023-05-11. I've opened https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/23699 as a follow-up to investigate the increase in client connections.
Current Status
More information will be added as we investigate the issue. For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.
📚 References and helpful links
Recent Events (available internally only):
- Feature Flag Log - Chatops to toggle Feature Flags Documentation
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Deployment Guidance
- Deployments Log | Gitlab.com Latest Updates
- Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.