When One Docker Swarm Replica Became Unreachable Over an Overlay Network: A Production Case With Traefik

https://dz2cdn1.dzone.com/storage/article-thumb/19194667-thumb.jpg

Context

The incident occurred in the production backend infrastructure of a mobile application. External HTTP traffic was handled by Traefik, deployed on Docker Swarm manager nodes. Traefik ran in swarmMode, used providers.docker, was configured to use the mgp_default network, and had lbswarm disabled so that routing used the required overlay network rather than the Swarm VIP.

One of the critical services was mgp_router-app. It was an entry-point service with two replicas deployed to preserve availability if one of them failed.

Visit Advertiser websiteGO TO PAGE

The service used placement constraints, max replicas per node = 1, and a Traefik health check configured for /actuator/health on port 8080. This meant we relied on external health checking and strictly controlled replica placement across nodes.

Swarm-level load balancingwas intentionally disabled. We needed routing control at the Traefik layer, along with the ability to quickly remove unhealthy backends based on their health...

Copyright of this story solely belongs to dzone.com. To see the full text click HERE

Read more

http://www.techmeme.com/img/techmeme_sq328.png

OpenAI says the FBI arrested one of its staffers after the company found a hidden recording device in its offices and used its models to identify who placed it

Featured Podcasts Training Data: David Silver and Lasse Espeholt of Ineffable Intelligence: A Superlearner for the Age of Experience Sequoia Capital partners host conversations with leading AI builders and researchers to develop a deeper understanding of the evolving technologies and their implications. Subscribe to Training Data. Invest Like the Best: