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
There is no such setting for Tempo for some reason 🤔, and current behavior can potentially lead to a situation when Tempo fulfills the worker's disk capacity.
Is this desired 🤔? If not, can you please add this option to the Tempo Helm chart 🙏🏼?
The text was updated successfully, but these errors were encountered:
Rohlik
changed the title
[tempo] - compactor is not aligned with other components
[tempo] - Persistence for compactor is not aligned with other components
Jan 6, 2025
Hi there 👋🏼,
compactor within Tempo seems to be slightly off in setting persistence compared to other components like Mimir or Loki 🧐. Please take a look at the related code snippets below.
Mimir: https://github.com/grafana/mimir/blob/bec189c4ba11111a251c3b48253704736761ad23/operations/helm/charts/mimir-distributed/values.yaml#L2282-L2320
Loki: https://github.com/grafana/loki/blob/226e9f101aab2faf32b2d6b0c93f6e5832782c25/production/helm/loki/values.yaml#L2430-L2459
There is no such setting for Tempo for some reason 🤔, and current behavior can potentially lead to a situation when Tempo fulfills the worker's disk capacity.
Is this desired 🤔? If not, can you please add this option to the Tempo Helm chart 🙏🏼?
The text was updated successfully, but these errors were encountered: