krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-09-29 16:08:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs auto-sync

Browse Source
This commit is contained in:
qdrant
2023-04-11 23:50:20 +00:00
parent a36aa80ef6
commit 8bc6a3fe89
8 changed files with 125 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/snapshots.md
+9 -1
View File
@@ -115,7 +115,7 @@ Recovering in cluster mode is more sophisticated, as Qdrant should maintain cons
As the information about created collections is stored in the consensus, even a newly attached cluster node will automatically create collections.
Recovering non-existing collections with snapshots won't make this collection known to the consensus.
To recover snpshot in this case one can use snapshot recovery API:
To recover snapshot in this case one can use snapshot recovery API:
```http
PUT /collections/<collection_name>/snapshots/recover
@@ -133,6 +133,14 @@ client = QdrantClient("qdrant-node-2", port=6333)
client.recover_snapshot("collection_name", "http://qdrant-node-1:6333/collections/collection_name/snapshots/snapshot-2022-10-10.shapshot")
```
The recovery snapshot can also be uploaded as a file to the cluster:
```bash
curl -X POST 'http://qdrant-node-1:6333/collections/collection_name/snapshots/upload' \
-H 'Content-Type:multipart/form-data' \
-F 'snapshot=@/path/to/snapshot-2022-10-10.shapshot'
```
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.