From d8220066dcc95197f679b0958fa7d6cef2607ec2 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Tue, 14 Nov 2023 21:40:47 +0100 Subject: [PATCH] docs/Cluster-VictoriaMetrics.md: clarify how -storage.vminsertConnsShutdownDuration command-line flag works --- README.md | 5 ++++- docs/Cluster-VictoriaMetrics.md | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9d8e64bf1..b30c7fa3f 100644 --- a/README.md +++ b/README.md @@ -473,7 +473,10 @@ during the config update / version upgrade. In this case the following 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. -Make sure that the `-storage.vminsertConnsShutdownDuration` is smaller than the graceful timeout configured at the system which manages `vmstorage` +In this case `vmstorage` increases the interval between gradual closing of `vminsert` connections during graceful shutdown. +This reduces data ingestion slowdown during rollout restarts. + +Make sure that the `-storage.vminsertConnsShutdownDuration` is smaller than the graceful shutdown timeout configured at the system which manages `vmstorage` (e.g. Docker, Kubernetes, systemd, etc.). Otherwise the system may kill `vmstorage` node before it finishes gradual closing of `vminsert` connections. ### Minimum downtime strategy diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index e0d883f1d..b1430dec2 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -484,7 +484,10 @@ during the config update / version upgrade. In this case the following 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. -Make sure that the `-storage.vminsertConnsShutdownDuration` is smaller than the graceful timeout configured at the system which manages `vmstorage` +In this case `vmstorage` increases the interval between gradual closing of `vminsert` connections during graceful shutdown. +This reduces data ingestion slowdown during rollout restarts. + +Make sure that the `-storage.vminsertConnsShutdownDuration` is smaller than the graceful shutdown timeout configured at the system which manages `vmstorage` (e.g. Docker, Kubernetes, systemd, etc.). Otherwise the system may kill `vmstorage` node before it finishes gradual closing of `vminsert` connections. ### Minimum downtime strategy