From bf7d06c0051db265cc305591f00c26c81c278ae8 Mon Sep 17 00:00:00 2001 From: Vika Date: Fri, 8 Dec 2023 12:29:46 +0000 Subject: [PATCH] update wiki pages --- Cluster-VictoriaMetrics.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Cluster-VictoriaMetrics.md b/Cluster-VictoriaMetrics.md index 949f65e..bd96c7c 100644 --- a/Cluster-VictoriaMetrics.md +++ b/Cluster-VictoriaMetrics.md @@ -552,7 +552,8 @@ The cluster works in the following way when some of `vmstorage` nodes are unavai This guarantees that the newly ingested data is properly saved if the healthy `vmstorage` nodes have enough CPU, RAM, disk IO and network bandwidth for processing the increased data ingestion workload. `vminsert` spreads evenly the additional data among the healthy `vmstorage` nodes in order to spread evenly - the increased load on these nodes. + the increased load on these nodes. During re-routing, healthy `vmstorage` nodes will experience higher resource usage + and increase in number of [active time series](https://docs.victoriametrics.com/FAQ.html#what-is-an-active-time-series). - `vmselect` continues serving queries if at least a single `vmstorage` nodes is available. It marks responses as partial for queries served from the remaining healthy `vmstorage` nodes,