From 6ca1b151343af048393bf6cbf9ec4dfb283f3b5f Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Wed, 16 Oct 2024 20:08:30 +0200 Subject: [PATCH] docs/VictoriaLogs/README.md: fix copy-n-paste typo: partitions in VictoriaLogs are per-day, not per-month --- docs/VictoriaLogs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/VictoriaLogs/README.md b/docs/VictoriaLogs/README.md index cd8d53b72..e2bc665e8 100644 --- a/docs/VictoriaLogs/README.md +++ b/docs/VictoriaLogs/README.md @@ -136,7 +136,7 @@ VictoriaLogs automatically creates the `-storageDataPath` directory on the first VictoriaLogs performs data compactions in background in order to keep good performance characteristics when accepting new data. These compactions (merges) are performed independently on per-day partitions. This means that compactions are stopped for per-day partitions if no new data is ingested into these partitions. -Sometimes it is necessary to trigger compactions for old partitions. In this case forced compaction may be initiated on the specified per-month partition +Sometimes it is necessary to trigger compactions for old partitions. In this case forced compaction may be initiated on the specified per-day partition by sending request to `/internal/force_merge?partition_prefix=YYYYMMDD`, where `YYYYMMDD` is per-day partition name. For example, `http://victoria-logs:9428/internal/force_merge?partition_prefix=20240921` would initiate forced merge for September 21, 2024 partition. The call to `/internal/force_merge` returns immediately, while the corresponding forced merge continues running in background.