You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lately, we've been continuously paged by the MimirHPAReachedMaxReplicas alert, mostly for the querier component. Currently this component has a maxReplicas number of 10 with its hpa and a default resources requests of 100m for CPU and 500Mi for the memory.
According to the following per-pod resources usage, CPU is fine but memory could use a little increase :
From our current understanding, the querier needs to scale whenever someone uses its installation's grafana, which would mean that it should scale down during the night. Because of this, I would advocate to increase the maxReplicas to 15 and slightly increase its default memory requests in the shared-configs repo (i;e something like 650~700Mi) to avoid having to increase the former forever.
The text was updated successfully, but these errors were encountered:
Lately, we've been continuously paged by the
MimirHPAReachedMaxReplicas
alert, mostly for thequerier
component. Currently this component has amaxReplicas
number of 10 with its hpa and a default resources requests of 100m for CPU and 500Mi for the memory.According to the following per-pod resources usage, CPU is fine but memory could use a little increase :
From our current understanding, the querier needs to scale whenever someone uses its installation's grafana, which would mean that it should scale down during the night. Because of this, I would advocate to increase the
maxReplicas
to 15 and slightly increase its default memory requests in theshared
-configs repo (i;e something like 650~700Mi) to avoid having to increase the former forever.The text was updated successfully, but these errors were encountered: