You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by vi...@apache.org on 2013/11/20 20:12:38 UTC
git commit: Fixed broken image links in mesos-architecture doc.
Updated Branches:
refs/heads/master 0fa399d9d -> 68e925400
Fixed broken image links in mesos-architecture doc.
From: Niklas Nielsen <ni...@qni.dk>
Review: https://reviews.apache.org/r/15719
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/68e92540
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/68e92540
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/68e92540
Branch: refs/heads/master
Commit: 68e925400ed737bebe65dee0e0297790cf5cbeac
Parents: 0fa399d
Author: Vinod Kone <vi...@twitter.com>
Authored: Wed Nov 20 11:12:22 2013 -0800
Committer: Vinod Kone <vi...@twitter.com>
Committed: Wed Nov 20 11:12:22 2013 -0800
----------------------------------------------------------------------
docs/mesos-architecture.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/68e92540/docs/mesos-architecture.md
----------------------------------------------------------------------
diff --git a/docs/mesos-architecture.md b/docs/mesos-architecture.md
index 3ead614..439a56d 100644
--- a/docs/mesos-architecture.md
+++ b/docs/mesos-architecture.md
@@ -4,7 +4,7 @@ layout: documentation
# Mesos Architecture
-
+
The above figure shows the main components of Mesos. Mesos consists of a *master* daemon that manages *slave* daemons running on each cluster node, and *mesos applications* (also called *frameworks*) that run *tasks* on these slaves.
@@ -16,7 +16,7 @@ A framework running on top of Mesos consists of two components: a *scheduler* th
The figure below shows an example of how a framework gets scheduled to run a task.
-
+
Let's walk through the events in the figure.
@@ -29,4 +29,4 @@ In addition, this resource offer process repeats when tasks finish and new resou
While the thin interface provided by Mesos allows it to scale and allows the frameworks to evolve independently, one question remains: how can the constraints of a framework be satisfied without Mesos knowing about these constraints? For example, how can a framework achieve data locality without Mesos knowing which nodes store the data required by the framework? Mesos answers these questions by simply giving frameworks the ability to **reject** offers. A framework will reject the offers that do not satisfy its constraints and accept the ones that do. In particular, we have found that a simple policy called delay scheduling, in which frameworks wait for a limited time to acquire nodes storing the input data, yields nearly optimal data locality.
-You can also read much more about the Mesos architecture in this [technical paper](http://mesos.berkeley.edu/mesos_tech_report.pdf).
\ No newline at end of file
+You can also read much more about the Mesos architecture in this [technical paper](http://mesos.berkeley.edu/mesos_tech_report.pdf).