-
Notifications
You must be signed in to change notification settings - Fork 630
Evaluating rule failed (consistency check failed because some blocks were not queried) #3191
Replies: 1 comment · 3 replies
-
Are the store-gateway replicas healthy? Are they going out of memory? |
Beta Was this translation helpful? Give feedback.
All reactions
-
We run it with 1 replica and no Ram limit but I will check more and provide more logs. But when
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Tnx @pracucci yes the err="inconsistent ring tokens information we have not set memory or CPU limit. what is the problem with the
And also once I saw this on the Grafana:
I delete the |
Beta Was this translation helpful? Give feedback.
All reactions
-
The error Be aware it contains the hostname and IP of your store-gateways. If that's a sensitive information then please redact it, but make sure each redacted store-gateway ID is still unique in the ring (so I will be able to correlate it with tokens). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have recorded rules with many time series for a
30d
time window and when Mimir wants to evaluate them fails. How can we tune it? which parameters shall we increase? or if we need to increase/add more CPU/RAM, to which Pod?I increased
max_fetched_chunks_per_query: 8000000
and that timestore-gateway
restarted several times as I inspected.Rule is like the below to have a sense:
Also, I see these logs in
store-gateway
logs of
query-frontend
:log of
querier
:Beta Was this translation helpful? Give feedback.
All reactions