You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by bm...@apache.org on 2016/02/23 18:54:24 UTC
mesos git commit: Updated the HA framework guide for TASK_KILLING.
Repository: mesos
Updated Branches:
refs/heads/master 1743ad4c2 -> 8b5137ddb
Updated the HA framework guide for TASK_KILLING.
Review: https://reviews.apache.org/r/43821
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/8b5137dd
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/8b5137dd
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/8b5137dd
Branch: refs/heads/master
Commit: 8b5137ddbb33417518dee32066c0fb552d05d046
Parents: 1743ad4
Author: Benjamin Mahler <bm...@apache.org>
Authored: Mon Feb 22 06:16:50 2016 +0100
Committer: Benjamin Mahler <bm...@apache.org>
Committed: Tue Feb 23 09:54:08 2016 -0800
----------------------------------------------------------------------
docs/high-availability-framework-guide.md | 6 ++++++
1 file changed, 6 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/8b5137dd/docs/high-availability-framework-guide.md
----------------------------------------------------------------------
diff --git a/docs/high-availability-framework-guide.md b/docs/high-availability-framework-guide.md
index 0d9c483..2cebdec 100644
--- a/docs/high-availability-framework-guide.md
+++ b/docs/high-availability-framework-guide.md
@@ -199,6 +199,12 @@ initial state and several possible terminal states:
* Note that the correctness of this technique depends on the fact that
messaging between the scheduler and the master is ordered.
+* The `TASK_KILLING` state is optional and is intended to indicate that the
+ request to kill the task has been received by the executor, but the task has
+ not yet been killed. This is useful for tasks that require some time to
+ terminate gracefully. Executors must not generate this state unless the
+ framework has the `TASK_KILLING_STATE` framework capability.
+
* There are several terminal states:
* `TASK_FINISHED` is used when a task completes successfully.