mesos-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From git-site-r...@apache.org
Subject mesos-site git commit: Updated the website built from mesos SHA: 3705306.
Date Wed, 18 Oct 2017 20:02:12 GMT
Repository: mesos-site
Updated Branches:
  refs/heads/asf-site 4a1d82a3f -> 7f63b70df


Updated the website built from mesos SHA: 3705306.


Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/7f63b70d
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/7f63b70d
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/7f63b70d

Branch: refs/heads/asf-site
Commit: 7f63b70df57293738f51180e301416b55f48e94d
Parents: 4a1d82a
Author: jenkins <builds@apache.org>
Authored: Wed Oct 18 20:02:10 2017 +0000
Committer: jenkins <builds@apache.org>
Committed: Wed Oct 18 20:02:10 2017 +0000

----------------------------------------------------------------------
 .../high-availability-framework-guide/index.html            | 9 +++++----
 .../latest/high-availability-framework-guide/index.html     | 9 +++++----
 2 files changed, 10 insertions(+), 8 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos-site/blob/7f63b70d/content/documentation/high-availability-framework-guide/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/high-availability-framework-guide/index.html b/content/documentation/high-availability-framework-guide/index.html
index cdca646..638de86 100644
--- a/content/documentation/high-availability-framework-guide/index.html
+++ b/content/documentation/high-availability-framework-guide/index.html
@@ -309,10 +309,11 @@ initial state and several possible terminal states:</p>
 master has received the framework&rsquo;s request to launch the task but the task
 has not yet started to run. In this state, the task&rsquo;s dependencies are
 fetched&mdash;for example, using the <a href="/documentation/latest/./fetcher/">Mesos
fetcher cache</a>.</p></li>
-<li><p>The <code>TASK_STARTING</code> state is optional and intended
primarily for use by
-custom executors. It can be used to describe the fact that a custom executor
-has learned about the task (and maybe started fetching its dependencies) but has
-not yet started to run it.</p></li>
+<li><p>The <code>TASK_STARTING</code> state is optional. It can be
used to describe the fact
+that an executor has learned about the task (and maybe started fetching its
+dependencies) but has not yet started to run it. Custom executors are
+encouraged to send it, to provide a more detailed description of the current
+task state to outside observers.</p></li>
 <li><p>A task transitions to the <code>TASK_RUNNING</code> state
after it has begun running
 successfully (if the task fails to start, it transitions to one of the
 terminal states listed below).</p>

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/7f63b70d/content/documentation/latest/high-availability-framework-guide/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/high-availability-framework-guide/index.html b/content/documentation/latest/high-availability-framework-guide/index.html
index a49c93b..d21f7cd 100644
--- a/content/documentation/latest/high-availability-framework-guide/index.html
+++ b/content/documentation/latest/high-availability-framework-guide/index.html
@@ -309,10 +309,11 @@ initial state and several possible terminal states:</p>
 master has received the framework&rsquo;s request to launch the task but the task
 has not yet started to run. In this state, the task&rsquo;s dependencies are
 fetched&mdash;for example, using the <a href="/documentation/latest/./fetcher/">Mesos
fetcher cache</a>.</p></li>
-<li><p>The <code>TASK_STARTING</code> state is optional and intended
primarily for use by
-custom executors. It can be used to describe the fact that a custom executor
-has learned about the task (and maybe started fetching its dependencies) but has
-not yet started to run it.</p></li>
+<li><p>The <code>TASK_STARTING</code> state is optional. It can be
used to describe the fact
+that an executor has learned about the task (and maybe started fetching its
+dependencies) but has not yet started to run it. Custom executors are
+encouraged to send it, to provide a more detailed description of the current
+task state to outside observers.</p></li>
 <li><p>A task transitions to the <code>TASK_RUNNING</code> state
after it has begun running
 successfully (if the task fails to start, it transitions to one of the
 terminal states listed below).</p>


Mime
View raw message