From 7a5000656eb572e6a9a0470e39ac2c8f2d122e20 Mon Sep 17 00:00:00 2001 From: Zakhar Bessarab Date: Fri, 24 May 2024 15:58:54 +0200 Subject: [PATCH] app/vmselect: update flag description (#6347) Update wording to highlight that cache is not persistent if flag is value is empty. Previously, it was not clear if cache is not used at all or just not persistent. Signed-off-by: hagen1778 --- docs/Cluster-VictoriaMetrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index 8e1816367..64a45c104 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -1307,7 +1307,7 @@ Below is the output for `/path/to/vmselect -help`: -blockcache.missesBeforeCaching int The number of cache misses before putting the block into cache. Higher values may reduce indexdb/dataBlocks cache size at the cost of higher CPU and disk read usage (default 2) -cacheDataPath string - Path to directory for cache files. Cache isn't saved if empty + Path to directory for cache files. By default, the cache is not persisted. -cacheExpireDuration duration Items are removed from in-memory caches after they aren't accessed for this duration. Lower values may reduce memory usage at the cost of higher CPU usage. See also -prevCacheRemovalPercent (default 30m0s) -cluster.tls