Menu

RabbitMQ on Kubernetes: Fixing “Failed to create dirty CPU scheduler thread” (Error 11)
📰

RabbitMQ on Kubernetes: Fixing “Failed to create dirty CPU scheduler thread” (Error 11)

Reading 0:00
15s threshold

We deploy RabbitMQ across single-node and three-node Kubernetes clusters in both staging and production environments to enable asynchronous messaging across our microservices architecture. High availability and predictable message queuing are critical to keeping our downstream processing pipelines operational.

A few weeks back, our infrastructure and SRE teams ran into a frustrating crash loop on one of our high-availability RabbitMQ statefulsets. RabbitMQ liveness probes kept failing randomly and repeatedly, throwing severe thread creation errors into the kubelet logs and causing unexpected pod restarts.

We observed this issue in at least five deployments.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.