centersl/docker-docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-03-27 06:18:55 +07:00
Code Issues Packages Projects Releases Wiki Activity

Update troubleshoot.md (#6228)

Browse Source
This commit is contained in:
Wang Jie
2018-03-16 00:19:27 +08:00
committed by Gwendolynne Barr
parent 5e3b80f611
commit 6a8c1c96fb
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
swarm/swarm_at_scale/troubleshoot.md
View File

@@ -2,7 +2,7 @@
advisory: swarm-standalone
hide_from_sitemap: true
description: Try Swarm at scale
keywords: docker, swarm, scale, voting, application, certificates
keywords: docker, swarm, scale, voting, application, certificates
redirect_from:
- /swarm/swarm_at_scale/05-troubleshoot/
title: Troubleshoot the application
@@ -79,7 +79,7 @@ to restart failed containers.
One way to automatically restart failed containers is to explicitly start them
with the `--restart=unless-stopped` flag. This tells the local Docker daemon
to attempt to restart the container if it unexpectedly exits. This only
works in situations where the node hosting the container and it's Docker daemon
works in situations where the node hosting the container and its Docker daemon
are still up. This cannot restart a container if the node hosting it has failed,
or if the Docker daemon itself has failed.
@@ -92,7 +92,7 @@ drops below 10, the tool attempts to start more.
In our simple voting-app example, the front-end is scalable and serviced by a
load balancer. In the event that one of the two web containers fails (or the
node that is hosting it fails), the load balancer stops routing requests to it and
send all requests to the surviving web container. This solution is highly scalable
sends all requests to the surviving web container. This solution is highly scalable
meaning you can have up to *n* web containers behind the load balancer.
## Interlock load balancer failures