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 <wwctrsrx@gmail.com>
This commit is contained in:
rtm0 2024-09-03 11:28:03 +03:00 committed by GitHub
parent 1b1e61030b
commit 4df243d530
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -2230,7 +2230,8 @@ func (is *indexSearch) searchMetricIDs(qt *querytracer.Tracer, tfss []*TagFilter
func errTooManyTimeseries(maxMetrics int) error { func errTooManyTimeseries(maxMetrics int) error {
return fmt.Errorf("the number of matching timeseries exceeds %d; "+ 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) "see https://docs.victoriametrics.com/#resource-usage-limits", maxMetrics)
} }