# Sidekiq jobs queueing duration SLO violation on all urgent shards (Severity 2) The Sidekiq queueing apdex on the low-urgency-cpu-bound shard is currently 99.36%, indicating that the proportion of jobs meeting their queueing duration targets has fallen below the defined SLO for the past 6 hours. This job backlog was caused by LockManager LWLock saturation on ci replica databases. We will add an additional replica in a follow-up to add more headroom. _This ticket was created to track_ [_INC-8367_](https://app.incident.io/gitlab/incidents/8367)_, by_ [_incident.io_](https://app.incident.io) 🔥