mesos git commit: Change documentation to reflect the removal of the slave checkpoint flag.

[nn...@apache.org]

Repository: mesos
Updated Branches:
  refs/heads/master a0aa123f7 -> 9e5a32701


Change documentation to reflect the removal of the slave checkpoint flag.

Review: https://reviews.apache.org/r/31300


Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/9e5a3270
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/9e5a3270
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/9e5a3270

Branch: refs/heads/master
Commit: 9e5a32701bb4f47ade6ad2ed3fd0cc8d544115b4
Parents: a0aa123
Author: Joerg Schad <jo...@mesosphere.io>
Authored: Mon Feb 23 11:12:57 2015 -0800
Committer: Niklas Q. Nielsen <ni...@mesosphere.io>
Committed: Mon Feb 23 11:12:57 2015 -0800

----------------------------------------------------------------------
 docs/slave-recovery.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos/blob/9e5a3270/docs/slave-recovery.md
----------------------------------------------------------------------
diff --git a/docs/slave-recovery.md b/docs/slave-recovery.md
index bc0e748..57eb786 100644
--- a/docs/slave-recovery.md
+++ b/docs/slave-recovery.md
@@ -15,18 +15,20 @@ Mesos slave could be restarted for an upgrade or due to a crash. This feature is
 
 Slave recovery works by having the slave checkpoint enough information (e.g., Task Info, Executor Info, Status Updates) about the running tasks and executors to local disk. Once the slave ***and*** the framework(s) enable checkpointing, any subsequent slave restarts would recover the checkpointed information and reconnect with the executors. Note that if the host running the slave process is rebooted all the executors/tasks are killed.
 
-> NOTE: To enable slave recovery both the slave and the framework should explicitly request checkpointing.
+> NOTE: To enable recovery the framework should explicitly request checkpointing.
 > Alternatively, a framework that doesn't want the disk i/o overhead of checkpointing can opt out of checkpointing.
 
 
 ## Enabling slave checkpointing
+> NOTE: From Mesos 0.22.0 slave checkpointing will be automatically enabled for all slaves.
 
 As part of this feature, 4 new flags were added to the slave.
 
 * `checkpoint` :  Whether to checkpoint slave and frameworks information
-                  to disk [Default: false].
+                  to disk [Default: true].
     - This enables a restarted slave to recover status updates and reconnect
       with (--recover=reconnect) or kill (--recover=kill) old executors.
+    > NOTE: From Mesos 0.22.0 this flag will be removed as it will be enabled for all slaves.
 
 	* `strict` : Whether to do recovery in strict mode [Default: true].
 		* If strict=true, any and all recovery errors are considered fatal.
@@ -45,7 +47,7 @@ As part of this feature, 4 new flags were added to the slave.
     reconnect to the slave will self-terminate.
     NOTE: This flag is only applicable when `--checkpoint` is enabled.
 
-> NOTE: If checkpointing is enabled on the slave, but none of the frameworks have enabled checkpointing,
+> NOTE: If none of the frameworks have enabled checkpointing,
 > executors/tasks of frameworks die when the slave dies and are not recovered.
 
 A restarted slave should re-register with master within a timeout (currently, 75s). If the slave takes longer