From 9f4e86ac2fcdd5682a44620a8d98572f2817647b Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Thu, 4 Jun 2020 20:19:06 +0300 Subject: [PATCH] docs/Cluster-VictoriaMetrics.md: update stale info about replication --- docs/Cluster-VictoriaMetrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index 1bb069b04..b02f31ef6 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -344,7 +344,7 @@ Due to `KISS` cluster version of VictoriaMetrics has no the following "features" - Fragile gossip protocols. See [failed attempt in Thanos](https://github.com/improbable-eng/thanos/blob/030bc345c12c446962225221795f4973848caab5/docs/proposals/completed/201809_gossip-removal.md). - Hard-to-understand-and-implement-properly [Paxos protocols](https://www.quora.com/In-distributed-systems-what-is-a-simple-explanation-of-the-Paxos-algorithm). -- Complex replication schemes, which may go nuts in unforesseen edge cases. The replication is offloaded to the underlying durable replicated storage +- Complex replication schemes, which may go nuts in unforesseen edge cases. See [replication docs](#replication-and-data-safety) for details. such as [persistent disks in Google Compute Engine](https://cloud.google.com/compute/docs/disks/#pdspecs). - Automatic data reshuffling between storage nodes, which may hurt cluster performance and availability. - Automatic cluster resizing, which may cost you a lot of money if improperly configured.