Prometheus query error 400 Bad Request after changing label selectors

white angel statue on brown wooden floor

Problem: Prometheus query returns 400 Bad Request after changing label selectors After a recent change to the AI model evaluation exporter, dashboard panels that query model_inference_latency_seconds, model_accuracy, and model_tokens_total started failing with HTTP 400 responses from the Prometheus query API. The error payload typically looks like: { “status”:”error”, “errorType”:”bad_data”, “error”:”parse error at char 27: unexpected character ‘\\’ in … Read more

OpenAI GPT-4o API rate limit exceeded during Kubernetes rolling update

a cell phone sitting on top of a laptop computer

OpenAI GPT‑4o API Rate Limit Exceeded During Kubernetes Rolling Update Problem Description (Symptoms and Impact) During a rolling update of the text‑generation microservice on GKE, a burst of 429 Too Many Requests responses was observed. The symptoms included: Log entries such as: [WARN] request_id=abc123 – OpenAI API returned 429 – Rate limit exceeded – retry_after=30s Failed … Read more

Weaviate replica node sync lag after canary deployment

cable network

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

Docker container memory allocation failure during multi-region replication

a golden docker logo on a black background

Docker Container Memory Allocation Failure During Multi‑Region Replication Problem Description During a scheduled multi‑region data replication job, Docker containers that host the replication agents repeatedly terminate with out‑of‑memory (OOM) errors. The failure manifests as: 2024-07-15T03:12:47.321Z containerd[1234]: failed to create shim task: failed to start container: OCI runtime create failed: container_linux.go:380: starting container process caused “process_linux.go:449: … Read more

Milvus vector index loading fails with intermittent DNS resolution timeouts

brown and black bird flying under white clouds during daytime

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

Hugging Face Transformers vision token sequence exceeds max_position_embeddings

Transformer robot

Problem: Vision token sequence exceeds max_position_embeddings in Hugging Face Transformers When processing high‑resolution images with VisionEncoderDecoderModel, ViTModel or CLIPModel, the image is split into fixed‑size patches. Each patch becomes a token, and the total token count must be ≤ the model’s max_position_embeddings (e.g., 197 for ViT‑B/16, 512 for CLIP). In production pipelines that ingest variable‑resolution … Read more

CUDA OOM during long sequence inference on NVIDIA GPU

the nvidia logo is displayed on a table

Problem Description On‑premise LLM inference nodes equipped with NVIDIA GPUs (e.g., A100 40 GiB, RTX 3090 24 GiB) crash when processing prompts that exceed the pre‑allocated key‑value (KV) cache size. The failure manifests as a CUDA out‑of‑memory (OOM) exception during the attention kernel launch. Typical log excerpts: [2026-08-10 14:32:07] ERROR – torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 2.00 … Read more

Haystack scheduler pod placement failure due to insufficient GPU

brown round grass on green grass field during daytime

Problem Description In a Haystack deployment that runs multi‑GPU training jobs, the scheduler pod remains Pending with events such as: 0/5 nodes are available: 5 Insufficient gpu or FailedScheduling: pod has unschedulable: no nodes match node selector These failures prevent the haystack-scheduler from launching training workers, effectively blocking any multi‑GPU training pipeline. Root Cause Analysis … Read more

Mistral AI webhook timeout after 30 seconds pending async job

A close up of a cell phone on a table

Problem When using Mistral AI’s asynchronous completion endpoints, webhook callbacks that deliver the final inference result are intermittently failing. The failure manifests as a 30‑second timeout, after which the payload is dropped and the client receives no status update. The issue becomes pronounced under high traffic (≈500 RPS) where the API gateway’s rate limiting and connection‑pool … Read more