Sat. May 9th, 2026

How We Diagnosed a Hidden Scheduler Failure in a Docker Swarm Cluster Serving 2 Million Users


Context: 120 Nodes, Strict SLAs, and Legacy Infrastructure

Our team is responsible for the mobile backend infrastructure serving over 2 million registered users. The Docker Swarm cluster consists of 120 nodes: 5 manager nodes, 40 worker nodes, and the rest are infrastructure servers. The cluster runs about 50 services, totaling hundreds of replicas.

We inherited Swarm from the previous contractor. The client is not yet ready to migrate to Kubernetes, and Swarm is currently sufficient for the current scale. Services are distributed across nodes in groups and bound by labels: up to 4 worker nodes are allocated to heavier services, 2 to less loaded ones, and 1 to non-critical services. Nodes can host replicas of multiple services.

By uttu

Related Post

Leave a Reply

Your email address will not be published. Required fields are marked *