mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2026-05-25 12:37:46 +03:00
aba5205896
Previously, if the value of rentetionFilter was changed within the same retention, storage didn't start background merge for historical data. This commits changes this behaviour by writing applied filters into metadata.json. For backward-compatibility it reads content of appliedRetention.txt file. It should prevent from triggering background merge on storage update. If needed, manually remove appliedRetention.txt file from storage/data/PART folder and remove storage. Also, it properly applies retentionFilter for data back-filling. Previously, it was ignored and data outside of retention could be ingested. In addition, it changes scheduling of historical merges. Instead 2 separate background processes, storage launches a single thread. It reduces CPU resource and disk IO resources usage. Related issues: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8885 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4592