Repository navigation
feat: Per-bucket visibility of S3 connections and timeouts - #121
Merged
Merged
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The timeout warning misrepresents mixed retry failures, and independent rate limiters allow twice the stated combined warning budget.
2 open issues
What changed in this PR
This PR adds per-bucket visibility into S3 connection contention and restores timeout warnings, helping assess whether the shared connection pool needs per-bucket limits.
Changes:
- Adds bucket labels to connection-in-use and waiting gauges while retaining the shared permit pool.
- Adds rate-limited warnings with bucket, key, and size for deadline and terminal timeout failures.
- Adds a test for bucket-isolated in-use gauges and cleanup when permits are dropped.
| File | Description |
|---|---|
quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs |
Tracks permits by bucket, logs timeout outcomes, and tests gauge isolation. |
quickwit/quickwit-storage/src/metrics.rs |
Converts connection gauges to bucket-labelled metric vectors and updates their descriptions. |
Review effort: Balanced
Signed-off-by: Darkheir <raphael.cohen@sekoia.io>
Darkheir
force-pushed
the
feat/s3-per-bucket-visibility
branch
from
November 6, 2026 08:50
f4470a2 to
a67a855
Compare
rdettai-sk
approved these changes
Nov 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Description
All buckets share the same pool of GetObject connection permits (
QW_S3_MAX_GET_OBJECT_CONNECTIONS). During large bursts the pool saturates (up to 1023/1024 permits in use and 824 reads waiting on one searcher on fra1), but we cannot tell which bucket fills it, nor whether reads on other buckets suffer from it. Since #117, S3 timeouts also no longer log anything. This PR adds the bucket to both, to decide whether a per-bucket cap on connection permits is worth it.object_storage_get_object_connections_in_use/_waitingbucketlabel)get_slicedeadline exceededget_slicegiving up after a timed-out attemptEach warning is rate-limited to 60 per minute per searcher, so their counts are lower bounds.
Dashboards: per-searcher totals of the two gauges now need
sum by (kubernetes_pod_name) (...).How was this PR tested?
Added a test checking that a connection permit raises the gauge of its bucket only, and releases it when dropped. Existing timeout and deadline tests cover the warning paths.