This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/mesos-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a020423 Updated the website built from mesos SHA: 277d38d.
a020423 is described below
commit a020423bd136d17fc271b8690ad39593ce31ad75
Author: jenkins <[email protected]>
AuthorDate: Wed Apr 10 23:57:08 2019 +0000
Updated the website built from mesos SHA: 277d38d.
---
.../app-framework-development-guide/index.html | 14 +++++++++-----
.../latest/app-framework-development-guide/index.html | 14 +++++++++-----
2 files changed, 18 insertions(+), 10 deletions(-)
diff --git a/content/documentation/app-framework-development-guide/index.html
b/content/documentation/app-framework-development-guide/index.html
index 9b207ce..4cf7158 100644
--- a/content/documentation/app-framework-development-guide/index.html
+++ b/content/documentation/app-framework-development-guide/index.html
@@ -237,18 +237,22 @@ commands or Docker containers.</p>
<p>The current semantics of the default executor are as folows:</p>
-<p>– Tasks are launched as nested containers underneath the executor
container.</p>
+<p>– Task group is an atomic unit of deployment of a scheduler onto the
default executor.</p>
+
+<p>– 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.</p>
+
+<p>– All task groups' tasks are launched as nested containers underneath
the executor container.</p>
<p>– Task containers and executor container share resources like cpu,
memory,
network and volumes.</p>
-<p>– There is no resource isolation between different tasks within an
executor.
+<p>– Each task can have its own separate root file system (e.g., Docker
image).</p>
+
+<p>– There is no resource isolation between different tasks or task
groups within an executor.
Tasks' resources are added to the executor container.</p>
<p>– 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.</p>
-
-<p>– Multiple task groups are not supported.</p>
+ are killed automatically. The default executor commits suicide if there are
no active task groups.</p>
<p>Once the default executor is considered <strong>stable</strong>, the
command executor will be deprecated in favor of it.</p>
diff --git
a/content/documentation/latest/app-framework-development-guide/index.html
b/content/documentation/latest/app-framework-development-guide/index.html
index 5a480c1..5426637 100644
--- a/content/documentation/latest/app-framework-development-guide/index.html
+++ b/content/documentation/latest/app-framework-development-guide/index.html
@@ -237,18 +237,22 @@ commands or Docker containers.</p>
<p>The current semantics of the default executor are as folows:</p>
-<p>– Tasks are launched as nested containers underneath the executor
container.</p>
+<p>– Task group is an atomic unit of deployment of a scheduler onto the
default executor.</p>
+
+<p>– 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.</p>
+
+<p>– All task groups' tasks are launched as nested containers underneath
the executor container.</p>
<p>– Task containers and executor container share resources like cpu,
memory,
network and volumes.</p>
-<p>– There is no resource isolation between different tasks within an
executor.
+<p>– Each task can have its own separate root file system (e.g., Docker
image).</p>
+
+<p>– There is no resource isolation between different tasks or task
groups within an executor.
Tasks' resources are added to the executor container.</p>
<p>– 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.</p>
-
-<p>– Multiple task groups are not supported.</p>
+ are killed automatically. The default executor commits suicide if there are
no active task groups.</p>
<p>Once the default executor is considered <strong>stable</strong>, the
command executor will be deprecated in favor of it.</p>
