From cffd2c0dbbdfed6464f7382ae93cb030d4b61e2d Mon Sep 17 00:00:00 2001
From: timvisee <tim@visee.me>
Date: Tue, 28 Nov 2023 15:56:43 +0100
Subject: [PATCH] In recovery via API, mention snapshot priority section

---
 qdrant-landing/content/documentation/concepts/snapshots.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/qdrant-landing/content/documentation/concepts/snapshots.md b/qdrant-landing/content/documentation/concepts/snapshots.md
index a92a4799a..fcd3ceb83 100644
--- a/qdrant-landing/content/documentation/concepts/snapshots.md
+++ b/qdrant-landing/content/documentation/concepts/snapshots.md
@@ -221,8 +221,10 @@ curl -X POST 'http://qdrant-node-1:6333/collections/collection_name/snapshots/up
 
 ```
 
+<aside role="status">You probably want to set the <a href="#snapshot-priority">snapshot priority</a> explicitly during recovery to prevent unexpected results.</aside>
+
 Qdrant will extract shard data from the snapshot and properly register shards in the cluster.
-If there are other active replicas of the recovered shards in the cluster, Qdrant will replicate them to the newly recovered node to maintain data consistency.
+If there are other active replicas of the recovered shards in the cluster, Qdrant will replicate them to the newly recovered node by default to maintain data consistency.
 
 ### Snapshot priority