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

Missing request timeout config for ruler_storage #4835

Closed
KaiserNicols opened this issue Aug 19, 2022 · 2 comments
Closed

Missing request timeout config for ruler_storage #4835

KaiserNicols opened this issue Aug 19, 2022 · 2 comments

Comments

@KaiserNicols
Copy link

KaiserNicols commented Aug 19, 2022

Describe the bug
Observing timeouts when the Ruler makes a request to Azure storage (/api/v1/rules) to fetch the alert rules. We have roughly 60k rules in storage for a particular tenant, so could be a very large payload if everything comes in a single response.

I suspect the default request timeout is 30s, but I don't see a 'request_timeout' field for Azure in the ruler_storage config.

#4581 added some http configs for Azure storage, but not for a request timeout. I no longer see this in the Cortex docs, but previously there was ruler.storage.azure.request_timeout. This setting is still visible via the /config api.

I get this timeout in Postman as well.

To Reproduce
Run Cortex

  • Distributed mode on AKS, rendered with Helm
  • 1.13.0

Connect the ruler to an azure storage (via the ruler_storage config).
Upload a large amount of rules to storage
Try to have ruler fetch the rules (I believe this is done via /api/v1/rules)

Expected behavior
Ruler should fetch the alerts, and not get timed out.

@alvinlin123
Copy link
Contributor

alvinlin123 commented Sep 4, 2022

Hello, can you try the ruler-storage.azure.http.response-header-timeout to see if that works for you?

The ruler.storage.* config have been deprecated for a while, and is being removed from Cortex, that's why you don't see the config on the Cortex website now. ruler.storage.* is still supported in 1.13.0, but please migrate to using ruler_storage configuration instead.

@stale
Copy link

stale bot commented Jan 7, 2023

This issue has been automatically marked as stale because it has not had any activity in the past 60 days. It will be closed in 15 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 7, 2023
@stale stale bot closed this as completed Apr 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants