Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable -blocks-storage.bucket-store.max-concurrent-queue-timeout by default #8496

Merged

Conversation

pracucci
Copy link
Collaborator

What this PR does

I propose to enable -blocks-storage.bucket-store.max-concurrent-queue-timeout by default, with a value of 5s. That's how we run it at Grafana Cloud and looks working fine. The rationale is that if the store-gateway concurrency is hit, it probably means the store-gateway is overloaded and we prefer to fast fail so that the querier will retry on another store-gateway (3 store-gateways will be tried, assuming RF=3).

Which issue(s) this PR fixes or relates to

N/A

Checklist

  • Tests updated.
  • Documentation added.
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
  • about-versioning.md updated with experimental features.

…efault

Signed-off-by: Marco Pracucci <marco@pracucci.com>
@pracucci pracucci requested review from tacole02 and a team as code owners June 24, 2024 10:39
Copy link
Contributor

@dimitarvdimitrov dimitarvdimitrov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@pracucci pracucci merged commit 0b95a7e into main Jun 24, 2024
29 checks passed
@pracucci pracucci deleted the set-blocks-storage.bucket-store.max-concurrent-queue-timeout branch June 24, 2024 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants