You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by tn...@apache.org on 2015/12/10 02:00:33 UTC
mesos git commit: Fix comments in TaskHealthStatus message proto.
Repository: mesos
Updated Branches:
refs/heads/master bde2f4d84 -> 1a64fb2e5
Fix comments in TaskHealthStatus message proto.
Review: https://reviews.apache.org/r/40954
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/1a64fb2e
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/1a64fb2e
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/1a64fb2e
Branch: refs/heads/master
Commit: 1a64fb2e58172642015e5dcc9d74d143b189eecf
Parents: bde2f4d
Author: Timothy Chen <tn...@apache.org>
Authored: Thu Dec 10 08:58:57 2015 +0800
Committer: Timothy Chen <tn...@apache.org>
Committed: Thu Dec 10 09:00:26 2015 +0800
----------------------------------------------------------------------
src/messages/messages.proto | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/1a64fb2e/src/messages/messages.proto
----------------------------------------------------------------------
diff --git a/src/messages/messages.proto b/src/messages/messages.proto
index 178d757..b66bac1 100644
--- a/src/messages/messages.proto
+++ b/src/messages/messages.proto
@@ -661,12 +661,11 @@ message Archive {
/**
- * Message describing task current health status that is sent by
- * the task health checker to the command executor.
- * The command executor reports the task status back to the
- * on each receive. If the health checker configured failure
- * condition meets, then `kill_task` flag will be set to true which
- * the executor on message receive will kill the task.
+ * Message describing a task's current health status, which is sent by
+ * the health check program to the executor.
+ * On each receive, if the number of consecutive failed health checks
+ * meets the `consecutive_failure` configuration, then `kill_task`
+ * flag will be set to true.
*/
message TaskHealthStatus {
required TaskID task_id = 1;
@@ -676,7 +675,7 @@ message TaskHealthStatus {
// Flag to initiate task kill.
optional bool kill_task = 3 [default = false];
- // Number of consecutive counts in current status.
+ // Number of consecutive failures observed by the health check program.
// This will not be populated if task is healthy.
optional int32 consecutive_failures = 4;
}