scheduling

RabbitMQ scheduler pod unschedulable during disaster recovery failover

by
a rack of servers in a server room

Problem – RabbitMQ Scheduler Pod Unschedulable During Disaster Recovery Failover During a planned disaster‑recovery (DR) failover, the RabbitMQ rabbitmq-scheduler pod repeatedly enters the Pending state with the following event: Warning FailedScheduling 2m30s (x5 over 5m) default-scheduler 0/3 nodes are available: 3 node(s) had insufficient memory, 3 node(s) had taint {dr/secondary=true:NoSchedule}, and 3 node(s) had pod … Read more

TorchServe pods pending after custom scheduler can’t match GPU resource requests

by
a purple and black background with a purple and black logo

Problem – TorchServe Pods Remain Pending When Using a Custom Scheduler In a Kubernetes cluster that hosts GPU‑enabled node pools, a real‑time inference service is deployed with TorchServe. The deployment succeeds, but the resulting pods stay in Pending state indefinitely. The custom scheduler (configured via a scheduler profile or extender) reports that it cannot find … Read more

Weaviate scheduler pods pending due to node selector mismatch in GKE

by
a rack of servers in a server room

Problem In a Google Kubernetes Engine (GKE) cluster running a Weaviate deployment, the weaviate-scheduler pods remain in the Pending state indefinitely. The kubectl describe pod output shows a scheduling failure related to node selector constraints, despite apparent node capacity. Root Cause The Weaviate Helm chart defines a nodeSelector for the scheduler component that targets a … Read more

Haystack scheduler pod placement failure due to insufficient GPU

by
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

Kubernetes scheduler failing to place AI pods on AMD GPU edge nodes

by
Amd ryzen 6000 series processor on circuit board background

Kubernetes Scheduler Failing to Place AI Pods on AMD GPU Edge Nodes Problem Description In a remote edge site the AI inference workload never leaves the Pending state. Typical scheduler messages include: 0/5 nodes are available: 5 node(s) didn’t match node selector. Insufficient amd.com/gpu: 0/5 nodes are available: 5 node(s) have insufficient resources. scheduler: no … Read more

Elasticsearch scheduler pod failed to place due to insufficient resources

by
a close-up of a server room

Problem Description In an air‑gapped Kubernetes cluster the Elasticsearch scheduler pod (managed by the Elastic Cloud on Kubernetes (ECK) operator) remains in Pending with events such as: Events: Type Reason Age From Message —- —— —- —- ——- Warning FailedScheduling 2m default-scheduler 0/5 nodes are available: 5 Insufficient cpu. Warning FailedScheduling 2m default-scheduler 0/5 nodes … Read more

Kubernetes scheduler pod placement failure after autoscaling

by
a rack of servers in a server room

Problem Description The Claude inference service experiences a cascade of pending pods during traffic spikes. Typical symptoms observed in the kubectl get pods -n claude-prod output are: NAME READY STATUS RESTARTS AGE claude-infer-7f9c9d8c9f-abcde 0/1 Pending 0 2m30s claude-infer-7f9c9d8c9f-fghij 0/1 Pending 0 2m30s … Relevant scheduler events (extracted from kubectl describe pod <pod>) contain the following … Read more