2023-05-03: Gitaly apdex dip on node file-38
Customer Impact
One Gitaly node experienced intermittent slowness.
Current Status
Performance is back to normal.
The 3 waves of slowness lasted for a few minutes each and were caused by CPU saturation. During graceful restarts of gitaly (such as during deployments), there is a window of time where an already in progress abusive workload temporarily gets to consume more machine resources than intended. A few mitigations are possible, and we are considering which is the best option. Supporting analysis is ongoing.
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.