Imported from qdrant/skills (
skills/qdrant-monitoring/debugging/SKILL.md). Install upstream withnpx skills add qdrant/skills --skill debugging. Copyright stays with the author.
How to Debug Qdrant with Metrics
First check optimizer status. Most production issues trace back to active optimizations competing for resources. If optimizer is clean, check memory, then request metrics.
Optimizer Stuck or Too Slow
Use when: optimizer running for hours, not finishing, or showing errors.
- Use the
/collections/{collection_name}/optimizationsendpoint (v1.17+) to see queued and running optimizations and their progress; add?with=queued,completed,idle_segmentsfor the full lists Optimization monitoring - Web UI has an Optimizations tab with timeline view and per-task duration metrics Web UI
- If
optimizer_statusshows an error in collection info, check logs for disk full or corrupted segments - Large merges and HNSW rebuilds legitimately take hours on big datasets. Check progress before assuming it's stuck.
Memory Seems Too High
Use when: memory exceeds expectations, node crashes with OOM, or memory keeps growing.
- Watch the process memory metrics on
/metrics:memory_resident_bytes,memory_allocated_bytes, andprocess_major_page_faults_totalNode metrics - Qdrant uses two types of RAM: resident memory (data structures, quantized vectors) and OS page cache (cached disk reads). Page cache filling available RAM is normal. Memory article
- If resident memory (RSSAnon) exceeds 80% of total RAM, investigate
- Check
/telemetryfor per-collection point counts and vector configurations. For a per-component breakdown of RAM, page cache, and disk use, callGET /collections/{collection_name}/memoryor open the Web UI's Memory tab (v1.18+) Memory usage - Estimate expected memory per component (vectors, HNSW index, ID tracker, payload indexes) for the structures kept in RAM, plus about 20% headroom, and compare it with actual usage Capacity planning
- Common causes of unexpected growth: quantized vectors pinned in RAM (
memory: pinnedon Qdrant 1.19 or newer,always_ram: trueon 1.18 or older), too many payload indexes, largemax_segment_sizeduring optimization
Queries Are Slow
Use when: queries slower than expected and you need to identify the cause.
- Slow request log (v1.16+, always on): surfaces individual slow queries with timing breakdown. It's per node and resets on restart, so query every node in a cluster by using
GET /profiler/slow_requestsSlow request log - Use the
rest_responses_duration_secondshistogram (v1.8+;grpc_responses_duration_secondsfor gRPC) for latency percentiles, rather than the avg and max gauges. Add?per_collection=trueto/metricsto break them down by collection Per-collection API metrics - Check optimizer status first. Active optimizations compete for CPU and I/O, degrading search latency.
- Check segment count via collection info. Too many unmerged segments after bulk upload causes slower search.
- Compare filtered vs unfiltered query times. Large gap means missing payload index. Payload index
What NOT to Do
- Ignore optimizer status when debugging slow queries (most common root cause)
- Assume memory leak when page cache fills RAM (normal OS behavior)
- Make config changes while optimizer is running (causes cascading re-optimizations)
- Blame Qdrant before checking if bulk upload just finished (unmerged segments)
