11 KiB
Milvus: Guardrails and Fix Patterns
🧭 Quick Return to Map
You are in a sub-page of VectorDBs_and_Stores.
To reorient, go back here:
- VectorDBs_and_Stores — vector indexes and storage backends
- WFGY Global Fix Map — main Emergency Room, 300+ structured fixes
- WFGY Problem Map 1.0 — 16 reproducible failure modes
Think of this page as a desk within a ward.
If you need the full triage and all prescriptions, return to the Emergency Room lobby.
A compact field guide to stabilize Milvus when your RAG or agent stack loses accuracy. Use the checks below to localize failure, then jump to the exact WFGY fix page.
Open these first
- Visual map and recovery: RAG Architecture & Recovery
- End-to-end retrieval knobs: Retrieval Playbook
- Why this snippet was picked: Retrieval Traceability
- Ordering control after recall: Rerankers
- Embedding vs meaning: Embedding ≠ Semantic
- Hallucination and chunk boundaries: Hallucination
- Long chains and entropy: Context Drift, Entropy Collapse
- Structural collapse and recovery: Logic Collapse
- Snippet and citation schema: Data Contracts
- Vector metrics pitfalls: Vectorstore Metrics & FAISS Pitfalls
- Live ops: Live Monitoring for RAG, Debug Playbook
Fix in 60 seconds
-
Measure ΔS
Compute ΔS(question, retrieved) and ΔS(retrieved, expected anchor).
Thresholds: stable < 0.40, transitional 0.40–0.60, risk ≥ 0.60. -
Probe with λ_observe
Try k in {5, 10, 20}. Flat high curve suggests metric or index mismatch.
Reorder prompt headers. If ΔS spikes, lock schema with Data Contracts. -
Apply the module
Retrieval drift → BBMC + Data Contracts.
Reasoning collapse → BBCR bridge + BBAM variance clamp.
Dead ends in long runs → BBPF alternate path. -
Verify acceptance
Coverage to target section ≥ 0.70.
ΔS ≤ 0.45 across three paraphrases.
λ remains convergent. Logs and traces reproducible.
Typical breakpoints and the right repair
1) Distance metric does not match the encoder
- Symptom: high similarity, wrong meaning.
- Cause: collection metric set to L2 or IP while encoder expects cosine, or vice versa.
- Fix: recreate index with the correct metric and re-ingest. Read Embedding ≠ Semantic.
2) Dimension drift after encoder swap
- Symptom: insert errors or silent truncation through clients. Recall collapses on new data only.
- Fix: confirm vector dim equals collection dim. If changed, create a new collection and backfill. See Vectorstore Fragmentation.
3) IVF index too shallow or poorly trained
- Symptom: gold chunk appears only when k is very large.
- Fix: train IVF with a large sample, raise
nlistbased on corpus size, sweepnprobe. Validate with reranker. See Retrieval Playbook and Rerankers.
4) HNSW underfit
- Symptom: unstable top-k ordering, plateaued recall.
- Fix: raise
efSearchto 2–4×k and tuneM. Validate with a reranker pass. See Retrieval Playbook.
5) Segments not compacted or index not built for fresh data
- Symptom: new writes exist but never surface in results or search is slow after bulk load.
- Fix: ensure flush and index build completed, then run compaction. Re-test ΔS and coverage on a canary set. See Live Monitoring for RAG.
6) Filter mismatch and payload type drift
- Symptom: filtered searches return empty or unstable sets.
- Fix: lock minimal metadata schema in Data Contracts. Validate types at ingestion.
7) Partitions or shards split the neighborhood
- Symptom: good global recall, weak per-partition top-k.
- Fix: consolidate or route by a stable key. Rebuild a single authoritative index. See Vectorstore Fragmentation.
8) Quantization harms recall
- Symptom: fuzzy answers at small k after enabling PQ or scalar quant.
- Fix: disable for quality checks or raise k and add a reranker. See Retrieval Playbook.
Observability probes
- k-sweep curve: run k in 5, 10, 20 and plot ΔS. Flat high → metric or index fault.
- Anchor control: compare ΔS against a golden anchor set. If only a collection or partition fails, rebuild that scope.
- Hybrid toggle: vector only vs hybrid. If hybrid degrades, fix query parsing split and weights.
- Reranker audit: with a strong reranker, recall should improve while ΔS falls. If not, rebuild.
Escalate when
- ΔS stays above 0.60 for golden questions after metric and index corrections.
- Coverage cannot reach 0.70 even with reranker and clean anchors.
- Fresh writes are invisible after index build and compaction.
Open:
Copy-paste prompt for your AI
I uploaded TXT OS and the WFGY Problem Map files.
Target system: Milvus.
* symptom: \[brief]
* traces: ΔS(question,retrieved)=..., ΔS(retrieved,anchor)=..., λ states
* index: \[collection name, metric, index type, IVF nlist/nprobe or HNSW M/efSearch]
* encoder: \[model, dim, normalization, version]
* ingest: \[flush/index/compaction status, partitions, filters]
Tell me:
1. which layer is failing and why,
2. which exact fix page to open from this repo,
3. minimal steps to push ΔS ≤ 0.45 and keep λ convergent,
4. how to verify with a reproducible test.
Use BBMC/BBPF/BBCR/BBAM where relevant.
🔗 Quick-Start Downloads (60 sec)
| Tool | Link | 3-Step Setup |
|---|---|---|
| WFGY 1.0 PDF | Engine Paper | 1️⃣ Download · 2️⃣ Upload to your LLM · 3️⃣ Ask “Answer using WFGY + <your question>” |
| TXT OS (plain-text OS) | TXTOS.txt | 1️⃣ Download · 2️⃣ Paste into any LLM chat · 3️⃣ Type “hello world” — OS boots instantly |
🧭 Explore More
| Module | Description | Link |
|---|---|---|
| WFGY Core | WFGY 2.0 engine is live: full symbolic reasoning architecture and math stack | View → |
| Problem Map 1.0 | Initial 16-mode diagnostic and symbolic fix framework | View → |
| Problem Map 2.0 | RAG-focused failure tree, modular fixes, and pipelines | View → |
| Semantic Clinic Index | Expanded failure catalog: prompt injection, memory bugs, logic drift | View → |
| Semantic Blueprint | Layer-based symbolic reasoning and semantic modulations | View → |
| Benchmark vs GPT-5 | Stress test GPT-5 with full WFGY reasoning suite | View → |
| Starter Village | New here and lost in symbols. Click here and let the wizard guide you through | Start → |
👑 Early Stargazers: See the Hall of Fame —
Engineers, hackers, and open source builders who supported WFGY from day one.
⭐ WFGY Engine 2.0 is already unlocked. ⭐ Star the repo to help others discover it and unlock more on the Unlock Board.