From c329aacedf5f622e9671d81569e6ec07ce0ba3f9 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Fri, 13 Nov 2020 18:43:04 +0200 Subject: [PATCH] docs/Single-server-VictoriaMetrics.md: document `/internal/force_flush` endpoint --- docs/CHANGELOG.md | 2 ++ docs/Single-server-VictoriaMetrics.md | 3 ++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index ba302a75c..78bb807d3 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -13,6 +13,8 @@ * FEATURE: consistently return text-based HTTP responses such as `plain/text` and `application/json` with `charset=utf-8`. See https://github.com/VictoriaMetrics/VictoriaMetrics/pull/897 * FEATURE: update Go builder from v1.15.4 to v1.15.5. This should fix [these issues in Go](https://github.com/golang/go/issues?q=milestone%3AGo1.15.5+label%3ACherryPickApproved). +* FEATURE: added `/internal/force_flush` http handler for flushing recently ingested data from in-memory buffers to persistent storage. + See [troubleshooting docs](https://victoriametrics.github.io/#troubleshooting) for more details. * BUGFIX: do not return data points in the end of the selected time range for time series ending in the middle of the selected time range. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/887 and https://github.com/VictoriaMetrics/VictoriaMetrics/issues/845 diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index e96ebea1d..dd1d83edf 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -1211,7 +1211,8 @@ VictoriaMetrics also exposes currently running queries with their execution time * VictoriaMetrics buffers incoming data in memory for up to a few seconds before flushing it to persistent storage. This may lead to the following "issues": - * Data becomes available for querying in a few seconds after inserting. + * Data becomes available for querying in a few seconds after inserting. It is possible to flush in-memory buffers to persistent storage + by requesting `/internal/force_flush` http handler. * The last few seconds of inserted data may be lost on unclean shutdown (i.e. OOM, `kill -9` or hardware reset). See [this article for technical details](https://valyala.medium.com/wal-usage-looks-broken-in-modern-time-series-databases-b62a627ab704).