2024-03-25: StoreSecurityReportsWorker saturates pgbouncer pool, causing delays in UI
Customer Impact
They see delayed updated in the UI.
Current Status
We have disabled the StoreSecurityReportsWorker
(2024-03-25 12:24) for all customers since we had a high level of statement timeouts which resulted into pgbouncer saturation.
Our next steps:
-
@reprazent: Drop all the jobs for the
StoreSecurityReportsWorker
👉 #17754 (comment 1830329093) - @dawsmith: Escalate with the customer to understand why there was a large uptick of CI jobs resulting in large number of Security Report generation. (updates on internal note below)
-
@sarahwalker@devin : Enable theStoreSecurityReportsWorker
following https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/sidekiq/disabling-a-worker.md- Run:
/chatops run feature delete drop_sidekiq_jobs_StoreSecurityReportsWorker --ignore-feature-flag-consistency-check
- Confirm that we are running jobs: https://log.gprd.gitlab.net/app/r/s/Y15sy
- Run:
- @minac @bwill: Will work on deploying a fix for the customer.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: Human-friendly 1-sentence statement on impacted
- Service Impact: service:: labels of services impacted by this incident
- Impact Duration: start time UTC - end time UTC ( duration in minutes )
- Root cause: TBD
📚 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.