Files
computer-playbook/roles/svc-db-qdrant/Upgrade.md
kevinveenbirkenbachandClaude Opus 4.8 fe94f72b7e feat(svc-db): add central DB engine roles (redis, memcached, rabbitmq, elasticsearch, typesense, qdrant)
Shared single-host engine roles consumed via lookup('engine', ...), mirroring the central postgres/mariadb pattern: meta/services flags, overlay topology in meta/server, compose templates, per-consumer provisioning in 02_init. Lets apps drop their embedded sidecars and become unpinned/NFS-shareable in swarm.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-23 19:29:39 +02:00

23 lines
662 B
Markdown

# Qdrant Docker Upgrade
This guide explains how to safely upgrade the Qdrant Docker container between versions.
---
## Important
Qdrant storage is forward-compatible within a major line but a major upgrade may require a snapshot/restore. Pin `services.qdrant.version` and test before rolling forward in production.
## Backup
Create a snapshot of every collection first (`POST /collections/{name}/snapshots`).
## Restore
Bump the version, redeploy, then restore the snapshots into the new instance.
## References
- [Qdrant Snapshots](https://qdrant.tech/documentation/concepts/snapshots/)
- [Qdrant Docker Image](https://hub.docker.com/r/qdrant/qdrant)