docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typo in Swarm scheduling doc 

Moved from https://github.com/docker/swarm/pull/2490

Signed-off-by: Misty Stanley-Jones <misty@docker.com>
This commit is contained in:
Misty Stanley-Jones 2016-10-17 11:29:31 -07:00
parent 33ed334075
commit 86fca1cc91
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
swarm/scheduler/rescheduling.md
View File

@ -2,16 +2,12 @@
description: Swarm rescheduling description: Swarm rescheduling
keywords: keywords:
- docker, swarm, clustering, rescheduling - docker, swarm, clustering, rescheduling
menu:
main:
parent: swarm_sched
weight: 6
title: Rescheduling title: Rescheduling
--- ---
# Swarm Rescheduling # Swarm Rescheduling
You can set recheduling policies with Docker Swarm. A rescheduling policy You can set rescheduling policies with Docker Swarm. A rescheduling policy
determines what the Swarm scheduler does for containers when the nodes they are determines what the Swarm scheduler does for containers when the nodes they are
running on fail. running on fail.
@ -26,7 +22,7 @@ container when a node fails.
To set the `on-node-failure` policy with a `reschedule` environment variable: To set the `on-node-failure` policy with a `reschedule` environment variable:
```bash ```bash
$ docker run -d -e reschedule:on-node-failure redis $ docker run -d -e "reschedule=on-node-failure" redis
``` ```
To set the same policy with a `com.docker.swarm.reschedule-policies` label: To set the same policy with a `com.docker.swarm.reschedule-policies` label:
@ -40,14 +36,14 @@ $ docker run -d -l 'com.docker.swarm.reschedule-policies=["on-node-failure"]' re
You can use the `docker logs` command to review the rescheduled container You can use the `docker logs` command to review the rescheduled container
actions. To do this, use the following command syntax: actions. To do this, use the following command syntax:
``` ```bash
docker logs SWARM_MANAGER_CONTAINER_ID docker logs SWARM_MANAGER_CONTAINER_ID
``` ```
When a container is successfully rescheduled, it generates a message similar to When a container is successfully rescheduled, it generates a message similar to
the following: the following:
``` ```no-highlight
Rescheduled container 2536adb23 from node-1 to node-2 as 2362901cb213da321 Rescheduled container 2536adb23 from node-1 to node-2 as 2362901cb213da321
Container 2536adb23 was running, starting container 2362901cb213da321 Container 2536adb23 was running, starting container 2362901cb213da321
``` ```
@ -55,7 +51,7 @@ Container 2536adb23 was running, starting container 2362901cb213da321
If for some reason, the new container fails to start on the new node, the log If for some reason, the new container fails to start on the new node, the log
contains: contains:
``` ```no-highlight
Failed to start rescheduled container 2362901cb213da321 Failed to start rescheduled container 2362901cb213da321
``` ```