# Sidekiq queueing SLO violation on elasticsearch shard (Severity 4) **Problem**: Sidekiq queueing SLO was violated on the elasticsearch shard, with jobs delayed far beyond expected durations. **Impact**: Sidekiq jobs on the elasticsearch shard did not meet queueing duration targets, leading to degraded search performance and Apdex scores for several teams. **Causes**: Extremely long execution times (over 30 minutes) in the UpdateIndexUsedStorageBytesEventWorker due to N+1 database queries, resulting in large queue backlogs. **Response strategy**: We created a merge request to batch database queries in the affected worker, reducing query counts from thousands to just a few per execution. Progress is currently blocked by persistent pipeline failures, with more than ten retries so far. The fix will be deployed once the merge request succeeds. _This ticket was created to track_ [_INC-7594_](https://app.incident.io/gitlab/incidents/7594)_, by_ [_incident.io_](https://app.incident.io) 🔥