mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2025-01-10 15:14:09 +00:00
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>
(cherry picked from commit 4df243d530
)
This commit is contained in:
parent
42ad757ac4
commit
cd6f2e6efe
1 changed files with 2 additions and 1 deletions
|
@ -2385,7 +2385,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)
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue