Engineering Logs for Troubleshooting & Debugging
Problem Description A production Weaviate cluster exhibited a growing replica synchronization lag after a canary deployment that introduced a new Docker image and an updated vector index schema. The primary node continued to accept writes, but replica nodes reported the following errors in their logs: 2024-07-31T14:22:13Z replica_sync_timeout: replica did not acknowledge write within configured timeout. … Read more
Problem: Weaviate client batch size exceeded during document ingestion During a large‑scale ingestion run on a self‑hosted Weaviate instance (32 GB RAM, Docker Compose), the Python client started failing after a few hundred documents. The failure manifested as HTTP 413 “Payload Too Large” responses and a subsequent cascade of aborted GraphQL mutations, ultimately causing data loss. Typical … Read more
Problem – Weaviate Service Unavailable After TLS Certificate Expiration In a cloud‑managed Weaviate deployment (e.g., on AWS EKS or GKE) the API endpoint becomes unreachable shortly after the TLS/SSL certificate used by the Ingress controller or the ALB expires. Clients see errors such as: x509: certificate has expired or is not yet valid TLS handshake … Read more
Weaviate Persistent Volume Mount Failure in Hybrid Kubernetes Cluster Problem Description When deploying Weaviate via the official Helm chart in a hybrid Kubernetes cluster (on‑premises nodes mixed with AWS or Azure cloud nodes), the Weaviate pods get stuck in Init:CreateContainerConfigError or ContainerCreating state. The kubelet logs contain errors such as: MountVolume.SetUp failed for volume “weaviate-data” … Read more
Weaviate Multimodal Embedding Mismatch Across AWS Regions Problem Description (Symptoms and Impact) In a multi‑region Weaviate deployment (e.g., us-east-1 and eu-west-1) with cross‑region replication enabled, identical multimodal objects (image + text) produce divergent search results after replication. The most common observable artifacts are: Search recall drops up to 15 % for image‑text queries after a regional failover (see … Read more
Problem – Controller‑manager crashes with segmentation fault under high‑load inference In a multi‑node Weaviate cluster running on Kubernetes with GPU‑accelerated inference, the controller‑manager pod repeatedly terminates with a SIGSEGV during spikes of concurrent /v1/objects or /v1/graphql queries. The failure manifests as: Segmentation fault (core dumped) [signal SIGSEGV: segmentation fault] at 0x7f… in libtorch.so panic: runtime … Read more
Problem – Weaviate Container CrashLoopBackOff in Kubernetes A production deployment of Weaviate on a multi‑node Kubernetes cluster repeatedly enters CrashLoopBackOff. The pod terminates shortly after start, causing the service to be unavailable for queries. Typical symptoms observed in the cluster: Pod status: CrashLoopBackOff after a few seconds. Readiness probe errors such as: Readiness probe failed: … Read more
Problem Description In a production Weaviate deployment several CronJob resources are used: Nightly backup (02:00) Index compaction (02:30) Data synchronization (every 15 minutes) Operators observed the following symptoms: Backup logs contain “Failed to acquire lock for backup”. Kubernetes controller logs show “CronJob is already running” for the index job. Occasional “Backoff limit exceeded” events after the … Read more
Weaviate Streaming API Incomplete Results Under High Traffic Problem – Symptoms and Impact During peak load the /v1/objects/{className}/{id}/stream endpoint returns truncated JSON payloads or the client receives a connection reset by peer error. Typical observations include: Logs in Weaviate: 2024-05-12T14:23:07Z WARN streaming response incomplete: expected 12456 bytes, got 8421 API gateway (Kong) reports: 504 Gateway … Read more