You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by gi...@apache.org on 2017/10/12 16:15:22 UTC
mesos-site git commit: Updated the website built from mesos SHA:
f7cf56c.
Repository: mesos-site
Updated Branches:
refs/heads/asf-site 66e8b9230 -> f72583210
Updated the website built from mesos SHA: f7cf56c.
Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/f7258321
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/f7258321
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/f7258321
Branch: refs/heads/asf-site
Commit: f725832100dc81fb4f70d35fe7ced1b16cdc17ef
Parents: 66e8b92
Author: jenkins <bu...@apache.org>
Authored: Thu Oct 12 16:15:17 2017 +0000
Committer: jenkins <bu...@apache.org>
Committed: Thu Oct 12 16:15:17 2017 +0000
----------------------------------------------------------------------
.../index.html | 9 ++--
.../index.html | 9 ++--
.../documentation/latest/upgrades/index.html | 48 ++++++++++++++++++++
content/documentation/upgrades/index.html | 48 ++++++++++++++++++++
4 files changed, 106 insertions(+), 8 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/f7258321/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’s request to launch the task but the task
has not yet started to run. In this state, the task’s dependencies are
fetched—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/f7258321/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’s request to launch the task but the task
has not yet started to run. In this state, the task’s dependencies are
fetched—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/f7258321/content/documentation/latest/upgrades/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/upgrades/index.html b/content/documentation/latest/upgrades/index.html
index 2458461..972ffea 100644
--- a/content/documentation/latest/upgrades/index.html
+++ b/content/documentation/latest/upgrades/index.html
@@ -154,6 +154,39 @@ R Removed feature/behavior
</thead>
<tr>
<td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version-->
+ 1.5.x
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Mesos Core-->
+ <ul style="padding-left:10px;">
+ <li>C <a href="#1-5-x-task-starting">Built-int executors send a TASK_STARTING update</a></li>
+ </ul>
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Flags-->
+ <ul style="padding-left:10px;">
+ </ul>
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Framework API-->
+ <ul style="padding-left:10px;">
+ </ul>
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Module API-->
+ <ul style="padding-left:10px;">
+ </ul>
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Endpoints-->
+ <ul style="padding-left:10px;">
+ </ul>
+ </td>
+
+</tr>
+
+<tr>
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version-->
1.4.x
</td>
@@ -428,6 +461,21 @@ R Removed feature/behavior
</table>
+<h2>Upgrading from 1.4.x to 1.5.x</h2>
+
+<p><a name="1-5-x-task-starting"></a></p>
+
+<ul>
+<li>The built-in executors will now send a <code>TASK_STARTING</code> status update for
+every task they’ve successfully received and are about to start.
+The possibility of any executor sending this update has been documented since
+the beginning of Mesos, but prior to this version the built-in executors did
+not actually send it. This means that all schedulers using one of the built-in
+executors must be upgraded to expect <code>TASK_STARTING</code> updates before upgrading
+Mesos itself.</li>
+</ul>
+
+
<h2>Upgrading from 1.3.x to 1.4.x</h2>
<p><a name="1-4-x-ambient-capabilities"></a></p>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/f7258321/content/documentation/upgrades/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/upgrades/index.html b/content/documentation/upgrades/index.html
index 342c98e..4b1cb55 100644
--- a/content/documentation/upgrades/index.html
+++ b/content/documentation/upgrades/index.html
@@ -154,6 +154,39 @@ R Removed feature/behavior
</thead>
<tr>
<td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version-->
+ 1.5.x
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Mesos Core-->
+ <ul style="padding-left:10px;">
+ <li>C <a href="#1-5-x-task-starting">Built-int executors send a TASK_STARTING update</a></li>
+ </ul>
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Flags-->
+ <ul style="padding-left:10px;">
+ </ul>
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Framework API-->
+ <ul style="padding-left:10px;">
+ </ul>
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Module API-->
+ <ul style="padding-left:10px;">
+ </ul>
+ </td>
+
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Endpoints-->
+ <ul style="padding-left:10px;">
+ </ul>
+ </td>
+
+</tr>
+
+<tr>
+ <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version-->
1.4.x
</td>
@@ -428,6 +461,21 @@ R Removed feature/behavior
</table>
+<h2>Upgrading from 1.4.x to 1.5.x</h2>
+
+<p><a name="1-5-x-task-starting"></a></p>
+
+<ul>
+<li>The built-in executors will now send a <code>TASK_STARTING</code> status update for
+every task they’ve successfully received and are about to start.
+The possibility of any executor sending this update has been documented since
+the beginning of Mesos, but prior to this version the built-in executors did
+not actually send it. This means that all schedulers using one of the built-in
+executors must be upgraded to expect <code>TASK_STARTING</code> updates before upgrading
+Mesos itself.</li>
+</ul>
+
+
<h2>Upgrading from 1.3.x to 1.4.x</h2>
<p><a name="1-4-x-ambient-capabilities"></a></p>