Repository: mesos Updated Branches: refs/heads/master 90f3fec71 -> 0bd9f2bb2
Fixed typos in the oversubscription doc. Review: https://reviews.apache.org/r/36839 Project: http://git-wip-us.apache.org/repos/asf/mesos/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/0bd9f2bb Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/0bd9f2bb Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/0bd9f2bb Branch: refs/heads/master Commit: 0bd9f2bb2824157656c4364d7a1839270c79c565 Parents: 90f3fec Author: haosdent huang <[email protected]> Authored: Mon Jul 27 10:22:36 2015 -0700 Committer: Jie Yu <[email protected]> Committed: Mon Jul 27 10:22:37 2015 -0700 ---------------------------------------------------------------------- docs/oversubscription.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos/blob/0bd9f2bb/docs/oversubscription.md ---------------------------------------------------------------------- diff --git a/docs/oversubscription.md b/docs/oversubscription.md index f17d4d4..4ff1f65 100644 --- a/docs/oversubscription.md +++ b/docs/oversubscription.md @@ -48,7 +48,7 @@ resources such as cpu shares, bandwidth, etc. the regular launchTasks() API. To safe-guard frameworks that are not designed to deal with preemption, only frameworks registering with the `REVOCABLE_RESOURCES` capability set in its framework info will receive offers -with revocable resources. Further more, recovable resources cannot be +with revocable resources. Further more, revocable resources cannot be dynamically reserved and persistent volumes should not be created on revocable disk resources. @@ -92,8 +92,8 @@ instructions how to configure Mesos for oversubscription. ### Launching tasks using revocable resources -Launching tasks using recovable resources is done through the existing -`launchTasks` API. Revocable resources will have the `recovable` field set. See +Launching tasks using revocable resources is done through the existing +`launchTasks` API. Revocable resources will have the `revocable` field set. See below for an example offer with regular and revocable resources. ~~~{.json} @@ -301,5 +301,5 @@ The `fixed` resource estimator is enabled as follows: In the example above, a fixed amount of 14 cpus will be offered as revocable resources. -To select custom a resource estimator and QoS controller, please refer to the +To install a custom resource estimator and QoS controller, please refer to the [modules documentation](modules.md).
