Engineering Logs for Troubleshooting & Debugging
Milvus Vector Index Loading Fails with Intermittent DNS Resolution Timeouts Problem Statement In edge deployments where Milvus runs on resource‑constrained nodes (Raspberry Pi, Jetson, etc.), the vector index loading phase intermittently hangs. The underlying symptom is a DNS resolution failure for the Etcd and MinIO service endpoints, which manifests as: Log entries such as 2023/07/15 10:12:34 … Read more
Problem: Milvus node initialization fails due to port conflict in a multi‑region Kubernetes deployment When deploying Milvus across several AWS regions with Amazon EKS, the Init phase of the Milvus pods repeatedly aborts with errors such as: Error: listen tcp 0.0.0.0:19530: bind: address already in use grpc server start failed: failed to listen on port … Read more
Problem – Milvus Cloud Service Returns HTTP 429 Under High Query Load During a traffic spike the application receives responses such as: HTTP/1.1 429 Too Many Requests Content-Type: application/json { “code”: 429, “message”: “Rate limit exceeded”, “details”: “RPS limit of 1000 exceeded” } or the Milvus Python SDK throws: milvus.exceptions.ServerException: status=429, message=’Rate limit exceeded, please retry … Read more
Problem – Milvus ReplicaSet Scaling Failure Under High‑Concurrency Benchmark During a distributed performance benchmark of Milvus 2.x, the team attempted to increase the replicaCount of the QueryNode (and optionally the Proxy) to meet a target query throughput of ~10 k QPS. The scaling operation consistently failed: New QueryNode pods remained in Pending or entered CrashLoopBackOff. Existing … Read more