You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by ya...@apache.org on 2017/07/18 15:51:55 UTC
mesos git commit: Updated documentation for MESOS-6223.
Repository: mesos
Updated Branches:
refs/heads/master ae055b33c -> 1e4f30ed3
Updated documentation for MESOS-6223.
Review: https://reviews.apache.org/r/60925/
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/1e4f30ed
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/1e4f30ed
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/1e4f30ed
Branch: refs/heads/master
Commit: 1e4f30ed37fdf4050e3a8fe31831e71924a9f816
Parents: ae055b3
Author: Megha Sharma <ms...@apple.com>
Authored: Mon Jul 17 17:37:21 2017 -0700
Committer: Jiang Yan Xu <xu...@apple.com>
Committed: Tue Jul 18 08:51:26 2017 -0700
----------------------------------------------------------------------
CHANGELOG | 2 ++
docs/agent-recovery.md | 4 ++++
docs/upgrades.md | 7 +++++++
3 files changed, 13 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/1e4f30ed/CHANGELOG
----------------------------------------------------------------------
diff --git a/CHANGELOG b/CHANGELOG
index 978747f..9145339 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -2,6 +2,8 @@ Release Notes - Mesos - Version 1.4.0 (WIP)
-------------------------------------------
This release contains the following new features:
+ * [MESOS-6223] - Agents are now allowed to recover the agent ID
+ after a host reboot. See docs/upgrades.md for details.
* [MESOS-7477] - Linux ambient capabilites are now supported, so
frameworks can run tasks that use ambient capabilites to grant
http://git-wip-us.apache.org/repos/asf/mesos/blob/1e4f30ed/docs/agent-recovery.md
----------------------------------------------------------------------
diff --git a/docs/agent-recovery.md b/docs/agent-recovery.md
index 1b3f2d2..f8f9cae 100644
--- a/docs/agent-recovery.md
+++ b/docs/agent-recovery.md
@@ -31,6 +31,10 @@ Note that if the operating system on the agent is rebooted, all executors and
tasks running on the host are killed and are not automatically restarted when
the host comes back up.
+However the agent is allowed to recover its agent ID post a host reboot.
+In case the agent's recovery runs into agent info mismatch which may happen due to resource change associated with reboot, it'll fall back to recovering as a new agent (existing behavior).
+In other cases such as checkpointed resources (e.g. persistent volumes) being incompatible with the agent's resources the recovery will still fail (existing behavior).
+
## Framework Configuration
A framework can control whether its executors will be recovered by setting the `checkpoint` flag in its `FrameworkInfo` when registering with the master. Enabling this feature results in increased I/O overhead at each agent that runs tasks launched by the framework. By default, frameworks do **not** checkpoint their state.
http://git-wip-us.apache.org/repos/asf/mesos/blob/1e4f30ed/docs/upgrades.md
----------------------------------------------------------------------
diff --git a/docs/upgrades.md b/docs/upgrades.md
index dda55f9..349d8a1 100644
--- a/docs/upgrades.md
+++ b/docs/upgrades.md
@@ -50,6 +50,7 @@ We categorize the changes as follows:
<ul style="padding-left:10px;">
<li>A <a href="#1-4-x-ambient-capabilities">Container capabilities are made ambient if supported</a></li>
<li>A <a href="#1-4-x-bounding-capabilities">Support for explicit bounding capabilities</a></li>
+ <li>C <a href="#1-4-x-agent-recovery">Agent recovery post reboot</a></li>
</ul>
</td>
@@ -324,6 +325,12 @@ We categorize the changes as follows:
* Explicitly setting the bounding capabilities of a task independently of the effective capabilities is now supported. Frameworks can specifiy the task bounding capabilities by using the `LinuxInfo.bounding_capabilities` message. Operators can specify the default bounding capabilities using the agent `--bounding_capabilities` flag. This flag also specifies the maximum bounding set that a framework is allowed to specify.
+<a name="1-4-x-agent-recovery"></a>
+
+* Agent is now allowed to recover its agent ID post a host reboot. This prevents the unnecessary discarding of agent ID by prior Mesos versions. Notes about backwards compatibility:
+ * In case the agent's recovery runs into agent info mismatch which may happen due to resource change associated with reboot, it'll fall back to recovering as a new agent (existing behavior).
+ * In other cases such as checkpointed resources (e.g. persistent volumes) being incompatible with the agent's resources the recovery will still fail (existing behavior).
+
<a name="1-4-x-linuxinfo-capabilities"></a>
* The `LinuxInfo.capabilities` field has been deprecated in favor of `LinuxInfo.effective_capabilities`.