VictoriaMetrics/app/vmselect
Aliaksandr Valialkin a5302a6651 app/vmselect/promql: take into account the previous point when calculating max_over_time and min_over_time
This lines up with `first_over_time` function used in `rollup_candlestick`, so `rollup=low` always returns
the minimum value.

Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/204
2019-10-08 12:30:16 +03:00
..
deployment all: open-sourcing cluster version 2019-05-23 00:25:38 +03:00
netstorage app/vmselect/netstorage: hint the OS that tmpBlocksFile is read almost sequentially 2019-09-30 00:13:33 +03:00
prometheus app/vmselect/prometheus: do not adjust start and end args in /api/v1/query_range if nocache=1 arg is set 2019-09-04 13:10:17 +03:00
promql app/vmselect/promql: take into account the previous point when calculating max_over_time and min_over_time 2019-10-08 12:30:16 +03:00
main.go lib/fs: add MustStopDirRemover for waiting until pending directories are removed on graceful shutdown 2019-09-05 11:17:17 +03:00
Makefile all: small updates after PR #114 2019-07-24 17:43:43 +03:00
README.md all: open-sourcing cluster version 2019-05-23 00:25:38 +03:00

vmselect performs the following tasks:

  • Splits incoming selects to tasks for vmstorage nodes and issues these tasks to all the vmstorage nodes in the cluster.

  • Merges responses from all the vmstorage nodes and returns a single response.