From 1de9cf3da6d2f3098a20f326a834621a04181efe Mon Sep 17 00:00:00 2001 From: Vika Date: Thu, 7 Dec 2023 11:55:23 +0000 Subject: [PATCH] update wiki pages --- Troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index f125951..413b6c2 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -417,7 +417,7 @@ The most common sources of cluster instability are: see [replication and data safety docs](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#replication-and-data-safety) for details. -- Time series sharding. Received time series [are consistently sharded](https://docs.victoriametrics.com/vmalert.html#rules-backfilling) +- Time series sharding. Received time series [are consistently sharded](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#architecture-overview) by `vminsert` between configured `vmstorage` nodes. As a sharding key `vminsert` is using time series name and labels, respecting their order. If the order of labels in time series is constantly changing, this could cause wrong sharding calculation and result in un-even and sub-optimal time series distribution across available vmstorages. It is expected