docs: clarify steps for rollup cache purge for vmselects

Signed-off-by: hagen1778 <roman@victoriametrics.com>
(cherry picked from commit 5e38dde18d)
This commit is contained in:
hagen1778 2023-11-28 09:38:19 +01:00
parent 562a2ddffc
commit 46f5aeb7ab
No known key found for this signature in database
GPG Key ID: 3BF75F3741CA9640
2 changed files with 7 additions and 1 deletions

View File

@ -155,6 +155,8 @@ If you see unexpected or unreliable query results from VictoriaMetrics, then try
If you use Grafana, then this query arg can be specified in `Custom Query Parameters` field
at Prometheus datasource settings - see [these docs](https://grafana.com/docs/grafana/latest/datasources/prometheus/) for details.
If the problem was in the cache, try resetting it via [resetRollupCache handler](https://docs.victoriametrics.com/url-examples.html#internalresetrollupresultcache).
1. If you use cluster version of VictoriaMetrics, then it may return partial responses by default
when some of `vmstorage` nodes are temporarily unavailable - see [cluster availability docs](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#cluster-availability)
for details. If you want to prioritize query consistency over cluster availability,

View File

@ -631,7 +631,7 @@ curl -Is http://localhost:8428/internal/resetRollupResultCache
</div>
Cluster version of VictoriaMetrics::
Cluster version of VictoriaMetrics:
<div class="with-copy" markdown="1">
@ -639,6 +639,10 @@ Cluster version of VictoriaMetrics::
curl -Is http://<vmselect>:8481/select/internal/resetRollupResultCache
```
vmselect will propagate this call to the rest of the vmselects listed in its `-selectNode` cmd-line flag. If this
flag isn't set, then cache need to be purged from each vmselect individually.
</div>
### TCP and UDP