From 0e4b8833419ebf369c046860ce715d00fc00b54e Mon Sep 17 00:00:00 2001 From: Denys Holius <5650611+denisgolius@users.noreply.github.com> Date: Wed, 5 Jul 2023 10:43:12 +0300 Subject: [PATCH] docs: adds curl commands to clear the query cache (#4468) adds curl commands to clear query cache on vmselect/VM Single --- README.md | 3 +-- docs/README.md | 3 +-- docs/Single-server-VictoriaMetrics.md | 3 +-- docs/url-examples.md | 23 +++++++++++++++++++++++ 4 files changed, 26 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index c39b10c93a..3edb338e51 100644 --- a/README.md +++ b/README.md @@ -2060,8 +2060,7 @@ It is recommended disabling query cache with `-search.disableCache` command-line historical data with timestamps from the past, since the cache assumes that the data is written with the current timestamps. Query cache can be enabled after the backfilling is complete. -An alternative solution is to query `/internal/resetRollupResultCache` url after backfilling is complete. This will reset -the query cache, which could contain incomplete data cached during the backfilling. +An alternative solution is to query [/internal/resetRollupResultCache](https://docs.victoriametrics.com/url-examples.html#internalresetRollupResultCache) handler after the backfilling is complete. This will reset the query cache, which could contain incomplete data cached during the backfilling. Yet another solution is to increase `-search.cacheTimestampOffset` flag value in order to disable caching for data with timestamps close to the current time. Single-node VictoriaMetrics automatically resets response diff --git a/docs/README.md b/docs/README.md index d94f9c7f0e..4aec3925f5 100644 --- a/docs/README.md +++ b/docs/README.md @@ -2063,8 +2063,7 @@ It is recommended disabling query cache with `-search.disableCache` command-line historical data with timestamps from the past, since the cache assumes that the data is written with the current timestamps. Query cache can be enabled after the backfilling is complete. -An alternative solution is to query `/internal/resetRollupResultCache` url after backfilling is complete. This will reset -the query cache, which could contain incomplete data cached during the backfilling. +An alternative solution is to query [/internal/resetRollupResultCache](https://docs.victoriametrics.com/url-examples.html#internalresetRollupResultCache) handler after the backfilling is complete. This will reset the query cache, which could contain incomplete data cached during the backfilling. Yet another solution is to increase `-search.cacheTimestampOffset` flag value in order to disable caching for data with timestamps close to the current time. Single-node VictoriaMetrics automatically resets response diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 24ad77bc03..5a16d55bc0 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -2071,8 +2071,7 @@ It is recommended disabling query cache with `-search.disableCache` command-line historical data with timestamps from the past, since the cache assumes that the data is written with the current timestamps. Query cache can be enabled after the backfilling is complete. -An alternative solution is to query `/internal/resetRollupResultCache` url after backfilling is complete. This will reset -the query cache, which could contain incomplete data cached during the backfilling. +An alternative solution is to query [/internal/resetRollupResultCache](https://docs.victoriametrics.com/url-examples.html#internalresetRollupResultCache) handler after the backfilling is complete. This will reset the query cache, which could contain incomplete data cached during the backfilling. Yet another solution is to increase `-search.cacheTimestampOffset` flag value in order to disable caching for data with timestamps close to the current time. Single-node VictoriaMetrics automatically resets response diff --git a/docs/url-examples.md b/docs/url-examples.md index c9cac02db4..9124aa99f1 100644 --- a/docs/url-examples.md +++ b/docs/url-examples.md @@ -618,6 +618,29 @@ Additional information: * [How to send Influx data to VictoriaMetrics](https://docs.victoriametrics.com/#how-to-send-data-from-influxdb-compatible-agents-such-as-telegraf) * [URL Format](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#url-format) +## /internal/resetRollupResultCache + +**Resets the response cache for previously served queries. It is recommended to invoke after [backfilling](https://docs.victoriametrics.com/#backfilling) procedure.** + +Single-node VictoriaMetrics: +<div class="with-copy" markdown="1"> + +```console +curl -Is http://localhost:8428/internal/resetRollupResultCache +``` + +</div> + +Cluster version of VictoriaMetrics:: + +<div class="with-copy" markdown="1"> + +```console +curl -Is http://<vmselect>:8481/select/internal/resetRollupResultCache +``` + +</div> + ## TCP and UDP ### How to send data from OpenTSDB-compatible agents to VictoriaMetrics