2023-08-25: SidekiqQueueTooLarge - ElasticSearch
Customer Impact
Degradation of Advanced Search functionality on GitLab.com. Apdex for global search around 60%.
Current Status
Search ElasticSearch cluster started seeing high CPU saturation starting 22:30 UTC Aug 25: https://dashboards.gitlab.net/goto/N1cUw_RSR?orgId=1
This resulted in search box on gitlab.com to take too long to return a response and eventually giving 500s error code.
Indexing and ElasticSearch migrations were stopped and migration worker was disabled. A rolling restart was done at first but it didn't help in recovering and CPU was saturated back again quickly.
Later, all the running tasks were cancelled and a full cluster restart was performed to recover from the situation. Indexing was re-enabled afterwards and all the pending documents were indexed.
Search has been functional since 02:41 UTC Aug 26.
ToDo:
-
Re-enable elasticsearch migration worker 👉 #16237 (comment 1530836698)
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.