From 4df243d5307dfb2937e4ea1593bbfec92b1eda97 Mon Sep 17 00:00:00 2001 From: rtm0 <149964189+rtm0@users.noreply.github.com> Date: Tue, 3 Sep 2024 11:28:03 +0300 Subject: [PATCH] lib/storage: improve the message of the tooManyTimeseries error (#6893) ### Describe Your Changes This is a follow-up for #6836. Per @valyala's [comment](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6836#discussion_r1730291704), the error message does not reflect which flag needs to be adjusted. ### Checklist The following checks are **mandatory**: - [x ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev --- lib/storage/index_db.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lib/storage/index_db.go b/lib/storage/index_db.go index 3a37ebb54..9c88678c9 100644 --- a/lib/storage/index_db.go +++ b/lib/storage/index_db.go @@ -2230,7 +2230,8 @@ func (is *indexSearch) searchMetricIDs(qt *querytracer.Tracer, tfss []*TagFilter func errTooManyTimeseries(maxMetrics int) error { return fmt.Errorf("the number of matching timeseries exceeds %d; "+ - "either narrow down the search or increase -search.max* command-line flag values at vmselect; "+ + "either narrow down the search or increase -search.max* command-line flag values at vmselect "+ + "(the most likely limit is -search.maxUniqueTimeseries); "+ "see https://docs.victoriametrics.com/#resource-usage-limits", maxMetrics) }