Dead Replica Quorum Risk

critical

ReplicationUpdated Feb 23, 2026

Non-active replicas (collection_dead_replicas) approach or exceed the configured replication_factor minus write_consistency_factor, risking write failures and data availability.

Sources

Monitor Clusters - Qdrantqdrant.tech

Monitoring & Telemetry - Qdrantqdrant.tech

Technologies:

QdrantSymptoms of this issue are visible in Qdrant metrics and logs

KubernetesThe root cause of this issue originates in Kubernetes

How to detect:

Alert when collection_dead_replicas > 0 or when collection_active_replicas_min falls below the configured write_consistency_factor. Cross-reference with kube_pod_status_phase to identify failed pods.

Recommended action:

Investigate pod failures via kube_pod_container_status_last_terminated_reason. Restore failed replicas by scaling statefulsets or recovering from snapshots. Temporarily reduce write_consistency_factor if unavoidable.