Repository: mesos Updated Branches: refs/heads/master cb941fefc -> 9a5abd79b
Updated docs to use standard US-ASCII. Project: http://git-wip-us.apache.org/repos/asf/mesos/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/9a5abd79 Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/9a5abd79 Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/9a5abd79 Branch: refs/heads/master Commit: 9a5abd79b30891e0b704a72bd4c46d449a3a069f Parents: cb941fe Author: Adam B <[email protected]> Authored: Fri Jul 24 17:24:14 2015 -0700 Committer: Adam B <[email protected]> Committed: Fri Jul 24 17:24:14 2015 -0700 ---------------------------------------------------------------------- docs/operational-guide.md | 6 +++--- docs/reconciliation.md | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos/blob/9a5abd79/docs/operational-guide.md ---------------------------------------------------------------------- diff --git a/docs/operational-guide.md b/docs/operational-guide.md index 23b76ff..6347fca 100644 --- a/docs/operational-guide.md +++ b/docs/operational-guide.md @@ -23,7 +23,7 @@ For online reconfiguration of the log, see: [MESOS-683](https://issues.apache.or ### Increasing the quorum size As the size of a cluster grows, it may be desired to increase the quorum size for additional fault tolerance. -The following steps indicate how to increment the quorum size, using 3 â 5 masters as an example (quorum size 2 â 3): +The following steps indicate how to increment the quorum size, using 3 -> 5 masters as an example (quorum size 2 -> 3): 1. Initially, 3 masters are running with `--quorum=2` 2. Restart the original 3 masters with `--quorum=3` @@ -34,7 +34,7 @@ To increase the quorum by N, repeat this process to increment the quorum size N ### Decreasing the quorum size -The following steps indicate how to decrement the quorum size, using 5 â 3 masters as an example (quorum size 3 â 2): +The following steps indicate how to decrement the quorum size, using 5 -> 3 masters as an example (quorum size 3 -> 2): 1. Initially, 5 masters are running with `--quorum=3` 2. Remove 2 masters from the cluster, ensure they will not be restarted (See NOTE section above). Now 3 masters are running with `--quorum=3` @@ -44,4 +44,4 @@ To decrease the quorum by N, repeat this process to decrement the quorum size N ### Replacing a master -Please see the NOTE section above. So long as the failed master is guaranteed to not re-join the ensemble, it is safe to start a new master _with an empty log_ and allow it to catch up. \ No newline at end of file +Please see the NOTE section above. So long as the failed master is guaranteed to not re-join the ensemble, it is safe to start a new master _with an empty log_ and allow it to catch up. http://git-wip-us.apache.org/repos/asf/mesos/blob/9a5abd79/docs/reconciliation.md ---------------------------------------------------------------------- diff --git a/docs/reconciliation.md b/docs/reconciliation.md index 17537ba..89ddf5b 100644 --- a/docs/reconciliation.md +++ b/docs/reconciliation.md @@ -77,10 +77,10 @@ The technique for performing reconciliation should reconcile all non-terminal tasks, until an update is received for each task, using exponential backoff: 1. let `start = now()` -2. let `remaining = { T ϵ tasks | T is non-terminal }` +2. let `remaining = { T in tasks | T is non-terminal }` 3. Perform reconciliation: `reconcile(remaining)` 4. Wait for status updates to arrive (use truncated exponential backoff). For each update, note the time of arrival. -5. let `remaining = { T ϵ remaining | T.last_update_arrival() < start }` +5. let `remaining = { T in remaining | T.last_update_arrival() < start }` 6. If `remaining` is non-empty, go to 3. This reconciliation algorithm **must** be run after each (re-)registration.
