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

docs auto-sync

Browse Source
This commit is contained in:
qdrant
2022-11-15 19:50:18 +00:00
parent 295dcfc1c5
commit efbdd6e28a
1 changed files with 34 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/snapshots.md
+34
View File
@@ -69,6 +69,11 @@ Only available through the REST API for the time being.
## Restore snapshot
There is a difference in recovering snapshots in single-deployment node and distributed deployment mode.
### Recover in single deployment mode
Single deployment is simpler, you can recover any collection on the start-up and it will be immediately available in the service.
Restoring snapshots is done through the Qdrant CLI at startup time.
The main entry point is the `--snapshot` argument which accepts a list of pairs `<snapshot_file_path>:<target_collection_name>`
@@ -83,6 +88,35 @@ The target collection **must** be absent otherwise the program will exit with an
If you wish instead to overwrite an existing collection, use the `--force_snapshot` flag with caution.
### Recover in cluster deployment
*Available since v0.11.3*
Recovering in cluster mode is more sophisticated, as Qdrant should maintain consistency across peers even during the recovery process.
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:
```http
PUT /collections/<collection_name>/snapshots/recover
{
"location": "http://qdrant-node-1:6333/collections/collection_name/snapshots/snapshot-2022-10-10.shapshot"
}
```
```python
from qdrant_client import QdrantClient
client = QdrantClient(host="qdrant-node-2", port=6333)
client.recover_snapshot("collection_name", "http://qdrant-node-1:6333/collections/collection_name/snapshots/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.
## Snapshots for the whole storage
*Available since v0.8.5*