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/08/18 15:17:39 UTC
mesos-site git commit: Updated the website built from mesos SHA:
feef102.
Repository: mesos-site
Updated Branches:
refs/heads/asf-site 324a50c14 -> b4af79fac
Updated the website built from mesos SHA: feef102.
Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/b4af79fa
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/b4af79fa
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/b4af79fa
Branch: refs/heads/asf-site
Commit: b4af79fac8206840527efa7db09c7126baeac531
Parents: 324a50c
Author: jenkins <bu...@apache.org>
Authored: Fri Aug 18 15:17:37 2017 +0000
Committer: jenkins <bu...@apache.org>
Committed: Fri Aug 18 15:17:37 2017 +0000
----------------------------------------------------------------------
content/documentation/health-checks/index.html | 8 ++++----
content/documentation/latest/health-checks/index.html | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/b4af79fa/content/documentation/health-checks/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/health-checks/index.html b/content/documentation/health-checks/index.html
index df5117c..2942d8c 100644
--- a/content/documentation/health-checks/index.html
+++ b/content/documentation/health-checks/index.html
@@ -188,7 +188,7 @@ status updates are triggered if a certain condition is met, e.g., the value or
presence of a specific field in the check status changes.</p>
<p>When a built-in executor sends a task status update because the check or health
-check status has changed, it sets <code>TaskStatus.reason</code> to
+check status has changed, it sets <code>TaskStatus.reason</code> to
<code>REASON_TASK_CHECK_STATUS_UPDATED</code> or <code>REASON_TASK_HEALTH_CHECK_STATUS_UPDATED</code>
respectively. While sending such an update, the executor avoids shadowing other
data that might have been injected previously, e.g., a check update includes the
@@ -212,11 +212,11 @@ implementation for health checking that all built-in executors rely on.</p>
<p>When humans read data from a sensor, they may interpret these data and act on
them. For example, if they check air temperature, they usually interpret
-temperature readings and say whether it’s cold or warm outside; they may also
+temperature readings and say whether it’s cold or warm outside; they may also
act on the interpretation and decide to apply sunscreen or put on an extra
jacket.</p>
-<p>Similar reasoning can be applied to checking task’s state in Mesos:</p>
+<p>Similar reasoning can be applied to checking task’s state in Mesos:</p>
<ol>
<li>Perform a check.</li>
@@ -230,7 +230,7 @@ healthy or unhealthy.</li>
task healthy or not, and kill it after <code>consecutive_failures</code> have occurred.
Though efficient and scalable, this strategy is inflexible for the needs of
frameworks which may want to run an arbitrary check without Mesos interpreting
-the result in any way, for example, to transmit the task’s internal state
+the result in any way, for example, to transmit the task’s internal state
transitions and make global decisions.</p>
<p>Conceptually, a health check is a check with an interpretation and a kill
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/b4af79fa/content/documentation/latest/health-checks/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/health-checks/index.html b/content/documentation/latest/health-checks/index.html
index 28f2bcc..8545621 100644
--- a/content/documentation/latest/health-checks/index.html
+++ b/content/documentation/latest/health-checks/index.html
@@ -188,7 +188,7 @@ status updates are triggered if a certain condition is met, e.g., the value or
presence of a specific field in the check status changes.</p>
<p>When a built-in executor sends a task status update because the check or health
-check status has changed, it sets <code>TaskStatus.reason</code> to
+check status has changed, it sets <code>TaskStatus.reason</code> to
<code>REASON_TASK_CHECK_STATUS_UPDATED</code> or <code>REASON_TASK_HEALTH_CHECK_STATUS_UPDATED</code>
respectively. While sending such an update, the executor avoids shadowing other
data that might have been injected previously, e.g., a check update includes the
@@ -212,11 +212,11 @@ implementation for health checking that all built-in executors rely on.</p>
<p>When humans read data from a sensor, they may interpret these data and act on
them. For example, if they check air temperature, they usually interpret
-temperature readings and say whether it’s cold or warm outside; they may also
+temperature readings and say whether it’s cold or warm outside; they may also
act on the interpretation and decide to apply sunscreen or put on an extra
jacket.</p>
-<p>Similar reasoning can be applied to checking task’s state in Mesos:</p>
+<p>Similar reasoning can be applied to checking task’s state in Mesos:</p>
<ol>
<li>Perform a check.</li>
@@ -230,7 +230,7 @@ healthy or unhealthy.</li>
task healthy or not, and kill it after <code>consecutive_failures</code> have occurred.
Though efficient and scalable, this strategy is inflexible for the needs of
frameworks which may want to run an arbitrary check without Mesos interpreting
-the result in any way, for example, to transmit the task’s internal state
+the result in any way, for example, to transmit the task’s internal state
transitions and make global decisions.</p>
<p>Conceptually, a health check is a check with an interpretation and a kill