Statuses
What a vector store's status means, and what to do when it is Failed.
Status
A vector store's status is worked out from its servers: how many of them are ready compared with the number of replicas it should have.
| Status | Meaning |
|---|---|
| Creating | No server is ready yet — the vector store is new, or all its servers are starting. |
| Running | Every server is ready. |
| Updating | Some servers are ready and others are not: the vector store is being scaled up, or its servers are being replaced after a change. |
| Stopped | The vector store is stopped; it has no servers. |
| Failed | The vector store is not coming up on its own — see below. |
| Unknown | The platform could not read the servers' state. This says nothing about the vector store itself; look again shortly. |
Scaling & Resources on the Overview shows Replicas and Ready Replicas side by side.
When it is Failed
A vector store is Failed in two cases:
- No server was started within five minutes of creation. The platform hands the vector store to the Qdrant operator in the cluster, and the operator has not acted on it. This happens when the cluster has no working Qdrant operator — ask your platform administrator.
- No server is ready and a server cannot start — it cannot be scheduled on a node, it has failed, its container keeps crashing, or its image cannot be pulled, for example because the version tag does not exist.
The status clears by itself once the servers come up. After correcting a version, save it again in Runtime.