From 7f47713821f088d0dcdda70564b312c9a9b0083c Mon Sep 17 00:00:00 2001 From: hagen1778 Date: Thu, 3 Oct 2024 14:11:04 +0200 Subject: [PATCH] docs: add missing `-search.maxDeleteSeries` to vmselect flags Signed-off-by: hagen1778 --- docs/Cluster-VictoriaMetrics.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index defc27cdf..9adcaeea9 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -1562,6 +1562,8 @@ Below is the output for `/path/to/vmselect -help`: Log queries with execution time exceeding this value. Zero disables slow query logging. See also -search.logQueryMemoryUsage (default 5s) -search.maxConcurrentRequests int The maximum number of concurrent search requests. It shouldn't be high, since a single request can saturate all the CPU cores, while many concurrently executed requests may require high amounts of memory. See also -search.maxQueueDuration and -search.maxMemoryPerQuery (default 16) + -search.maxDeleteSeries int + The maximum number of time series, which can be deleted using /api/v1/admin/tsdb/delete_series. This option allows limiting memory usage (default 1000000) -search.maxExportDuration duration The maximum duration for /api/v1/export call (default 720h0m0s) -search.maxExportSeries int