From 50f790b5d7c9d8956e98b459c90b80de54c26be8 Mon Sep 17 00:00:00 2001
From: Aliaksandr Valialkin <valyala@gmail.com>
Date: Thu, 25 Mar 2021 21:03:29 +0200
Subject: [PATCH] docs/Cluster-VictoriaMetrics.md: mention that vmselect doesnt
 serve partial responses from export API

Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1148
---
 docs/Cluster-VictoriaMetrics.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md
index ffaf85bad7..68b729ccaf 100644
--- a/docs/Cluster-VictoriaMetrics.md
+++ b/docs/Cluster-VictoriaMetrics.md
@@ -272,6 +272,8 @@ the update process. See [cluster availability](#cluster-availability) section fo
   - `vminsert` re-routes incoming data from unavailable `vmstorage` nodes to healthy `vmstorage` nodes
   - `vmselect` continues serving partial responses if at least a single `vmstorage` node is available. If consistency over availability is preferred, then either pass `-search.denyPartialResponse` command-line flag to `vmselect` or pass `deny_partial_response=1` query arg in requests to `vmselect`.
 
+`vmselect` doesn't serve partial responses for API handlers returning raw datapoints - [`/api/v1/export*` endpoints](https://victoriametrics.github.io/#how-to-export-time-series), since users usually expect this data is always complete.
+
 Data replication can be used for increasing storage durability. See [these docs](#replication-and-data-safety) for details.