From 48a77b17110cae01f5fa1ee074a65019787efebf Mon Sep 17 00:00:00 2001 From: lixiaobing10051267 Date: Fri, 19 Aug 2016 16:56:34 +0800 Subject: [PATCH] It is orchestrator not scheduler to create swarm task Signed-off-by: lixiaobing10051267 Upstream-commit: cb9dfd391ba4df5c34f83f5070e0b685c99bf591 Component: engine --- components/engine/docs/swarm/how-swarm-mode-works/services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/engine/docs/swarm/how-swarm-mode-works/services.md b/components/engine/docs/swarm/how-swarm-mode-works/services.md index 0ae9807fd3..971c7adf24 100644 --- a/components/engine/docs/swarm/how-swarm-mode-works/services.md +++ b/components/engine/docs/swarm/how-swarm-mode-works/services.md @@ -61,7 +61,7 @@ that spawns a new container. A task is a one-directional mechanism. It progresses monotonically through a series of states: assigned, prepared, running, etc. If the task fails the -scheduler removes the task and its container and then creates a new task to +orchestrator removes the task and its container and then creates a new task to replace it according to the desired state specified by the service. The underlying logic of Docker swarm mode is a general purpose scheduler and