You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by ti...@apache.org on 2015/12/17 06:11:17 UTC
mesos git commit: Cleaned up link format in docs.
Repository: mesos
Updated Branches:
refs/heads/master ba9868c5a -> 5281049ac
Cleaned up link format in docs.
Links from one documentation page to another should not use absolute
URLs (e.g. http://mesos.apache.org/documentation/latest/...) for
several good reasons. For instance, absolute URLs break when the docs
are generated/previewed locally.
Review: https://reviews.apache.org/r/41493/
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/5281049a
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/5281049a
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/5281049a
Branch: refs/heads/master
Commit: 5281049ace0e52c9fcfc6ed20c124f55db98787d
Parents: ba9868c
Author: Neil Conway <ne...@gmail.com>
Authored: Thu Dec 17 06:10:28 2015 +0100
Committer: Till Toenshoff <to...@me.com>
Committed: Thu Dec 17 06:10:28 2015 +0100
----------------------------------------------------------------------
docs/allocation-module.md | 2 +-
docs/architecture.md | 6 +++---
docs/authentication.md | 2 +-
docs/clang-format.md | 2 +-
docs/effective-code-reviewing.md | 2 +-
docs/high-availability.md | 8 ++++----
6 files changed, 11 insertions(+), 11 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/5281049a/docs/allocation-module.md
----------------------------------------------------------------------
diff --git a/docs/allocation-module.md b/docs/allocation-module.md
index 1d0f4be..1dc1aba 100644
--- a/docs/allocation-module.md
+++ b/docs/allocation-module.md
@@ -65,4 +65,4 @@ mesos::modules::Module<Allocator> ExternalAllocatorModule(
createExternalAllocator);
~~~
-Refer to the [Mesos Modules documentation](http://mesos.apache.org/documentation/latest/modules/) for instructions how to compile and load a module in Mesos master.
+Refer to the [Mesos Modules documentation](/documentation/latest/modules/) for instructions on how to compile and load a module in Mesos master.
http://git-wip-us.apache.org/repos/asf/mesos/blob/5281049a/docs/architecture.md
----------------------------------------------------------------------
diff --git a/docs/architecture.md b/docs/architecture.md
index df750c7..d1b3c0e 100644
--- a/docs/architecture.md
+++ b/docs/architecture.md
@@ -6,11 +6,11 @@ layout: documentation
-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.
+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 frameworks* that run *tasks* on these slaves.
-The master enables fine-grained sharing of resources (cpu, ram, ...) across applications by making them *resource offers*. Each resource offer contains a list of <slave ID, resource1: amount1, resource2, amount2, ...>. The master decides *how many* resources to offer to each framework according to a given organizational policy, such as fair sharing, or strict priority. To support a diverse set of policies, the master employs a modular architecture that makes it easy to add new allocation modules via a plugin mechanism.
+The master enables fine-grained sharing of resources (CPU, RAM, ...) across frameworks by making them *resource offers*. Each resource offer contains a list of <slave ID, resource1: amount1, resource2, amount2, ...>. The master decides *how many* resources to offer to each framework according to a given organizational policy, such as fair sharing or strict priority. To support a diverse set of policies, the master employs a modular architecture that makes it easy to add new allocation modules via a plugin mechanism.
-A framework running on top of Mesos consists of two components: a *scheduler* that registers with the master to be offered resources, and an *executor* process that is launched on slave nodes to run the framework's tasks (see the [App/Framework development guide](app-framework-development-guide.md) for more details about application schedulers and executors). While the master determines **how many** resources are offered to each framework, the frameworks' schedulers select **which** of the offered resources to use. When a frameworks accepts offered resources, it passes to Mesos a description of the tasks it wants to run on them. In turn, Mesos launches the tasks on the corresponding slaves.
+A framework running on top of Mesos consists of two components: a *scheduler* that registers with the master to be offered resources, and an *executor* process that is launched on slave nodes to run the framework's tasks (see the [App/Framework development guide](app-framework-development-guide.md) for more details about framework schedulers and executors). While the master determines **how many** resources are offered to each framework, the frameworks' schedulers select **which** of the offered resources to use. When a frameworks accepts offered resources, it passes to Mesos a description of the tasks it wants to run on them. In turn, Mesos launches the tasks on the corresponding slaves.
## Example of resource offer
http://git-wip-us.apache.org/repos/asf/mesos/blob/5281049a/docs/authentication.md
----------------------------------------------------------------------
diff --git a/docs/authentication.md b/docs/authentication.md
index 1c22c54..5f13181 100644
--- a/docs/authentication.md
+++ b/docs/authentication.md
@@ -18,7 +18,7 @@ Mesos uses the [Cyrus SASL library](http://asg.web.cmu.edu/sasl/) to implement a
## Configuration
-The [configuration options](http://mesos.apache.org/documentation/latest/configuration/) that are used by the authentication mechanism are as follows:
+The [configuration options](/documentation/latest/configuration/) that are used by the authentication mechanism are as follows:
### Masters
http://git-wip-us.apache.org/repos/asf/mesos/blob/5281049a/docs/clang-format.md
----------------------------------------------------------------------
diff --git a/docs/clang-format.md b/docs/clang-format.md
index 0ad8dc3..206bc2c 100644
--- a/docs/clang-format.md
+++ b/docs/clang-format.md
@@ -6,7 +6,7 @@ layout: documentation
[ClangFormat](http://llvm.org/releases/3.5.1/tools/clang/docs/ClangFormat.html) is an automatic source code formatting tool which helps us focus on the code rather than the formatting.
-> The provided configurations try to honor the [Mesos C++ Style Guide](http://mesos.apache.org/documentation/latest/c++-style-guide/) as much as possible, but there are some limitations which require manual attention. Even with these limitations however, ClangFormat will be extremely useful for your workflow!
+> The provided configurations try to honor the [Mesos C++ Style Guide](/documentation/latest/c++-style-guide/) as much as possible, but there are some limitations which require manual attention. Even with these limitations however, ClangFormat will be extremely useful for your workflow!
## Setup
http://git-wip-us.apache.org/repos/asf/mesos/blob/5281049a/docs/effective-code-reviewing.md
----------------------------------------------------------------------
diff --git a/docs/effective-code-reviewing.md b/docs/effective-code-reviewing.md
index 25d7126..fdfafc7 100644
--- a/docs/effective-code-reviewing.md
+++ b/docs/effective-code-reviewing.md
@@ -22,7 +22,7 @@ to consider before sending review requests:
change clear in the review request, so the reviewer is not left
guessing. It is highly recommended to attach a JIRA issue with your
review for additional context.
-4. **Follow the [style guide](http://mesos.apache.org/documentation/latest/c++-style-guide/)
+4. **Follow the [style guide](/documentation/latest/c++-style-guide/)
and the style of code around you**.
5. **Do a self-review of your changes before publishing**: Approach it
from the perspective of a reviewer with no context. Is it easy to figure
http://git-wip-us.apache.org/repos/asf/mesos/blob/5281049a/docs/high-availability.md
----------------------------------------------------------------------
diff --git a/docs/high-availability.md b/docs/high-availability.md
index f1cd688..31aa662 100644
--- a/docs/high-availability.md
+++ b/docs/high-availability.md
@@ -2,7 +2,7 @@
layout: documentation
---
-# Mesos High Availability Mode
+# Mesos High-Availability Mode
If the Mesos master is unavailable, existing tasks can continue to execute, but new resources cannot be allocated and new tasks cannot be launched. To reduce the chance of this situation occurring, Mesos has a high-availability mode that uses multiple Mesos masters: one active master (called the _leader_ or leading master) and several _backups_ in case it fails. The masters elect the leader, with [Apache ZooKeeper](http://zookeeper.apache.org/) both coordinating the election and handling leader detection by masters, slaves, and scheduler drivers. More information regarding [how leader election works](http://zookeeper.apache.org/doc/trunk/recipes.html#sc_leaderElection) is available on the Apache Zookeeper website.
@@ -19,11 +19,11 @@ To put Mesos into high-availability mode:
* Start the mesos-slave binaries with `--master=zk://host1:port1,host2:port2,.../path`
- * Start any framework schedulers using the same `zk` path as in the last two steps. The SchedulerDriver must be constructed with this path, as shown in the [Framework Development Guide]( http://mesos.apache.org/documentation/latest/app-framework-development-guide/).
+ * Start any framework schedulers using the same `zk` path as in the last two steps. The SchedulerDriver must be constructed with this path, as shown in the [Framework Development Guide](/documentation/latest/app-framework-development-guide/).
From now on, the Mesos masters and slaves all communicate with ZooKeeper to find out which master is the current leading master. This is in addition to the usual communication between the leading master and the slaves.
-Refer to the [Scheduler API](http://mesos.apache.org/documentation/latest/app-framework-development-guide/) for how to deal with leadership changes.
+Refer to the [Scheduler API](/documentation/latest/app-framework-development-guide/) for how to deal with leadership changes.
## Component Disconnection Handling
When a network partition disconnects a component (master, slave, or scheduler driver) from ZooKeeper, the component's Master Detector induces a timeout event. This notifies the component that it has no leading master. Depending on the component, the following happens. (Note that while a component is disconnected from ZooKeeper, a master may still be in communication with slaves or schedulers and vice versa.)
@@ -43,7 +43,7 @@ When a network partition disconnects a slave from the leader:
* The slave fails health checks from the leader.
-* The leader marks the slave as deactivated and sends its tasks to the LOST state. The [Framework Development Guide](http://mesos.apache.org/documentation/latest/app-framework-development-guide/) describes these various task states.
+* The leader marks the slave as deactivated and sends its tasks to the LOST state. The [Framework Development Guide](/documentation/latest/app-framework-development-guide/) describes these various task states.
* Deactivated slaves may not re-register with the leader and are told to shut down upon any post-deactivation communication.