From 1ef6b7f32b82f2cd09ed2ef5a8d8b9bb35e263cd Mon Sep 17 00:00:00 2001 From: hagen1778 Date: Mon, 20 Nov 2023 10:14:57 +0100 Subject: [PATCH] docs: calrify version when vminsertConnsShutdownDuration was added Signed-off-by: hagen1778 --- docs/Cluster-VictoriaMetrics.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index b1430dec2..82276c020 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -483,7 +483,8 @@ during the config update / version upgrade. In this case the following strategy [rolling restarts](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#no-downtime-strategy), since they need to process higher load when some of `vmstorage` nodes are temporarily unavailable in the cluster. It is possible to reduce resource usage spikes by running more `vminsert` nodes and by passing bigger values -to `-storage.vminsertConnsShutdownDuration` command-line flag at `vmstorage` nodes. +to `-storage.vminsertConnsShutdownDuration` (available from [v1.95.0](https://docs.victoriametrics.com/CHANGELOG.html#v1950)) +command-line flag at `vmstorage` nodes. In this case `vmstorage` increases the interval between gradual closing of `vminsert` connections during graceful shutdown. This reduces data ingestion slowdown during rollout restarts.