This is an automated email from the ASF dual-hosted git repository.
vinodkone pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mesos.git
The following commit(s) were added to refs/heads/master by this push:
new 277d38d Updated documentation of default executor.
277d38d is described below
commit 277d38d7277f70bf3e90052b41eaa4740562a4ee
Author: Vinod Kone <[email protected]>
AuthorDate: Wed Apr 10 18:27:50 2019 -0500
Updated documentation of default executor.
Documented that it supports multiple task groups. Made other minor
adjustments.
---
docs/app-framework-development-guide.md | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/docs/app-framework-development-guide.md
b/docs/app-framework-development-guide.md
index 3648ab6..e64cd92 100644
--- a/docs/app-framework-development-guide.md
+++ b/docs/app-framework-development-guide.md
@@ -130,19 +130,23 @@ commands or Docker containers.
The current semantics of the default executor are as folows:
--- Tasks are launched as nested containers underneath the executor container.
+-- Task group is an atomic unit of deployment of a scheduler onto the default
executor.
+
+-- The default executor can run one or more task groups (since Mesos 1.2) and
each task group can be launched by the scheduler at different points in time.
+
+-- All task groups' tasks are launched as nested containers underneath the
executor container.
-- Task containers and executor container share resources like cpu, memory,
network and volumes.
+
+-- Each task can have its own separate root file system (e.g., Docker image).
--- There is no resource isolation between different tasks within an executor.
+-- There is no resource isolation between different tasks or task groups
within an executor.
Tasks' resources are added to the executor container.
-- If any of the tasks exits with a non-zero exit code, all the tasks in the
task group
- are killed and the executor shuts down.
-
--- Multiple task groups are not supported.
-
+ are killed automatically. The default executor commits suicide if there are
no active task groups.
+
Once the default executor is considered **stable**, the command executor will
be deprecated in favor of it.
