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
Is your feature request related to a problem? Please describe.
The component "purger" is only responsible for exposing 2 API endpoints. When called mimir will upload a marker in the bucket which will ultimately trigger the purge of the data. Apart from this the purger does nothing else.
Describe the solution you'd like
Migrate the purger to another component, the compactor for example.
Describe alternatives you've considered
To achieve the same behavior we could enable the module along with another one
Is your feature request related to a problem? Please describe.
The component "purger" is only responsible for exposing 2 API endpoints. When called mimir will upload a marker in the bucket which will ultimately trigger the purge of the data. Apart from this the purger does nothing else.
Describe the solution you'd like
Migrate the purger to another component, the compactor for example.
Describe alternatives you've considered
To achieve the same behavior we could enable the module along with another one
Additional context
In a not monolithic deployment this help save resource (pod or instance)
General idea come from slack channel: https://grafana.slack.com/archives/C039863E8P7/p1655914578345719
The text was updated successfully, but these errors were encountered: