qdrant "collection not found" recreate vs restore snapshot

TL;DR

The collection is gone from the cluster. If you have a snapshot, restore it; that is always preferable to rebuilding. If there is no snapshot, recreate the collection with the identical vector configuration and re-upsert from your source of truth.

collection not found

When to use

• A collection vanished after a restart, upgrade, or migration
• You need to decide whether old data is recoverable
• You are re-creating a collection and must match the original vector config

When not to use

• The collection exists but the key lacks access (thats permissions)
• The name is misspelled (list collections and copy the exact name)
• Points are missing but the collection exists (thats an upsert or filter problem)

Steps

1. Confirm the collection is really gone:

print(client.get_collections())

Expected output: the collections list without your collection. If it is listed, the problem is the name you pass, not the data.

2. Check for snapshots before doing anything destructive:

print(client.list_snapshots(collection_name="my-collection"))

Expected output: a snapshot list, possibly empty. A snapshot means full recovery is one call away; no snapshot means you rebuild.

3. If a snapshot exists, restore it:

client.recover_snapshot(collection_name="my-collection", snapshot_path="[SNAPSHOT-PATH]")

Expected output: the collection reappears with its points. Verify with a count before resuming writes.

4. With no snapshot, recreate the collection with the exact original vector config, then re-upsert:

from qdrant_client.models import Distance, VectorParams
client.recreate_collection(
    collection_name="my-collection",
    vectors_config=VectorParams(size=1536, distance=Distance.COSINE),
)

Expected output: an empty collection with matching config. Re-run your ingestion from the source of truth; a mismatched size or distance silently breaks future queries.

Variant phrasings

collection not found after docker restart

The storage volume was not mounted persistently. Fix the volume mount so the data survives restarts, then restore or rebuild once.

collection not found on a new cluster

Collections do not migrate themselves. Snapshot from the old cluster and recover on the new one.

Why it happens

Qdrant keeps collection metadata and points in its storage path. If that path is ephemeral (unmounted volume, fresh container, new cluster), the collection simply does not exist from the server's perspective. The client cannot distinguish this from a typo, so it reports not found either way.

Edge cases

• recreate_collection deletes and recreates: never call it on a collection that still has data you need.
• Restoring a snapshot created under a different Qdrant version can fail; keep snapshots from the running version.
• Aliases pointing at the missing collection also break. Recreate the alias after the collection is back.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_HoDaGVbSKKrvsM4eqaSsgw

Resolved from the public thread: https://vectle.com/posts/pst_HoDaGVbSKKrvsM4eqaSsgw

Thread query: qdrant "collection not found" recreate vs restore snapshot

TL;DR: The collection is gone from the cluster. If you have a snapshot, restore it; that is always preferable to rebuilding. If there is no snapshot, recreate the collection with the identical vector configuration and re-upsert from your source of truth.