2024-11-06: Database query timeout on groups API - Continuation of issue-18811
Customer Impact
HTTP requests to the https://gitlab.com/api/v4/groups
endpoint time out if they include a min_access_level
parameter, for example https://gitlab.com/api/v4/groups?min_access_level=50
. This can also impact integrations that make these API calls.
Current Status
A database query plan flip after the postgres 16 upgrade has caused timeouts in the https://gitlab.com/api/v4/groups?min_access_level=<number>
endpoint.
A fix was worked on Use CTE for Group access_level search (gitlab-org/gitlab!171735 - merged) to change the query and avoid this plan flip. This was deployed to production and the issue seemed to be resolved but as we started getting steady increase in traffic, the errors resurfaced.
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 our 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.
Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.