From d0bf4393a90c57ac76c3a0f704784db8c39ed453 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Mon, 24 Jun 2019 22:52:06 +0300 Subject: [PATCH] app/vmselect/promql: increase default value for -search.maxPointsPerTimeSeries from 10k to 30k This may be required for subqueries with small steps. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/77 --- app/vmselect/promql/eval.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/app/vmselect/promql/eval.go b/app/vmselect/promql/eval.go index 0b2eea289..64ab3c894 100644 --- a/app/vmselect/promql/eval.go +++ b/app/vmselect/promql/eval.go @@ -17,7 +17,7 @@ import ( ) var ( - maxPointsPerTimeseries = flag.Int("search.maxPointsPerTimeseries", 10e3, "The maximum points per a single timeseries returned from the search") + maxPointsPerTimeseries = flag.Int("search.maxPointsPerTimeseries", 30e3, "The maximum points per a single timeseries returned from the search") ) // The minimum number of points per timeseries for enabling time rounding. @@ -32,7 +32,7 @@ const minTimeseriesPointsForTimeRounding = 50 func ValidateMaxPointsPerTimeseries(start, end, step int64) error { points := (end-start)/step + 1 if uint64(points) > uint64(*maxPointsPerTimeseries) { - return fmt.Errorf(`too many points for the given step=%d, start=%d and end=%d: %d; cannot exceed %d points`, + return fmt.Errorf(`too many points for the given step=%d, start=%d and end=%d: %d; cannot exceed -search.maxPointsPerTimeseries=%d`, step, start, end, uint64(points), *maxPointsPerTimeseries) } return nil