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

store-gateway: promote index-header gate timeout setting to advanced #8667

Merged
merged 2 commits into from
Jul 10, 2024

Conversation

56quarters
Copy link
Contributor

What this PR does

Promote -blocks-storage.bucket-store.index-header.lazy-loading-concurrency-queue-timeout from experimental to stable and set a default value of 5s.

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.

@56quarters 56quarters marked this pull request as ready for review July 9, 2024 20:22
@56quarters 56quarters requested review from tacole02 and a team as code owners July 9, 2024 20:22
Promote `-blocks-storage.bucket-store.index-header.lazy-loading-concurrency-queue-timeout` from
experimental to stable and set a default value of `5s`.

Signed-off-by: Nick Pillitteri <[email protected]>
Signed-off-by: Nick Pillitteri <[email protected]>
@56quarters 56quarters force-pushed the 56quarters/index-header-timeout-default branch from 2222f50 to 542c90c Compare July 10, 2024 13:16
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

@56quarters 56quarters merged commit 51da3f3 into main Jul 10, 2024
29 checks passed
@56quarters 56quarters deleted the 56quarters/index-header-timeout-default branch July 10, 2024 15:04
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