mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
20e9598254
This should prevent from out of memory errors when big number of vmselect nodes send many concurrent requests to vmstorage The limit can be controlled at vmstorage via the following command-line flags: - search.maxConcurrentRequests - search.maxQueueDuration See https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#resource-usage-limits |
||
---|---|---|
.. | ||
bufferedwriter | ||
clusternative | ||
deployment | ||
graphite | ||
graphiteql | ||
multiarch | ||
netstorage | ||
prometheus | ||
promql | ||
querystats | ||
searchutils | ||
static/css | ||
vmui | ||
main.go | ||
Makefile | ||
README.md |
vmselect
performs the following tasks:
-
Splits incoming selects to tasks for
vmstorage
nodes and issues these tasks to all thevmstorage
nodes in the cluster. -
Merges responses from all the
vmstorage
nodes and returns a single response.
The vmui
directory contains static contents built from app/vmui package with make vmui-update
command. The vmui
page is available at http://<vmselect>:8481/select/<accountID>/vmui/
.