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

feat(ruler): add flags for the query frontend retries #10259

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

julienduchesne
Copy link
Member

@julienduchesne julienduchesne commented Dec 16, 2024

Currently, Mimir is hardcoded at 3 retries and 100ms as a minimum retry time. Could be useful to configure this

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

@julienduchesne julienduchesne force-pushed the julienduchesne/ruler-retries branch from 493f5d9 to e89f6db Compare December 16, 2024 20:04
Currently, Mimir is hardcoded at 3 retries and 100ms as a minimum retry time. Could be useful to configure this
@julienduchesne julienduchesne force-pushed the julienduchesne/ruler-retries branch from e89f6db to fb55d8e Compare December 16, 2024 20:05
@julienduchesne julienduchesne marked this pull request as ready for review December 16, 2024 20:05
@julienduchesne julienduchesne requested review from a team as code owners December 16, 2024 20:05
@chencs
Copy link
Contributor

chencs commented Dec 16, 2024

Should the config flags be experimental for now?

@julienduchesne
Copy link
Member Author

julienduchesne commented Dec 16, 2024

Should the config flags be experimental for now?

The new flags expose the existing retry config which is already enabled for everyone using the query frontend, which isn't an experimental feature from what I can see. It doesn't seem like they should be experimental, unless I'm misunderstanding 🤔.

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.

I assume you're adding those flags so you can experiment with different retry strategies. I'm also leaning towards making these experimental and removing the once we know what's the better setting.

@julienduchesne julienduchesne requested a review from a team December 17, 2024 14:56
@julienduchesne julienduchesne requested a review from a team December 18, 2024 00:21
@@ -2987,6 +2987,12 @@ Usage of ./cmd/mimir/mimir:
Override the default minimum TLS version. Allowed values: VersionTLS10, VersionTLS11, VersionTLS12, VersionTLS13
-ruler.query-frontend.grpc-client-config.tls-server-name string
Override the expected name on the server certificate.
-ruler.query-frontend.max-retries int
[experimental] Maximum number of retries for a single request. (default 3)
Copy link
Contributor

Choose a reason for hiding this comment

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

this is actually max attempts, right? So it includes the first try. That's my understanding from reading the dskit code. I think we should clarify the CLI flag then.

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.

left a suggest about the wording on the max retries, but otherwise LGTM, I don't need to see it again

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.

4 participants