Repository: spark
Updated Branches:
  refs/heads/branch-1.1 85e7c52ba -> 0690410e4


Docs: move HA subsections to a deeper indentation level

Makes the table of contents read better

Author: Andrew Ash <and...@andrewash.com>

Closes #2402 from ash211/docs/better-indentation and squashes the following 
commits:

ea0e130 [Andrew Ash] Move HA subsections to a deeper indentation level

(cherry picked from commit b3830b28f8a70224d87c89d8491c514c4c191d23)
Signed-off-by: Andrew Or <andrewo...@gmail.com>


Project: http://git-wip-us.apache.org/repos/asf/spark/repo
Commit: http://git-wip-us.apache.org/repos/asf/spark/commit/0690410e
Tree: http://git-wip-us.apache.org/repos/asf/spark/tree/0690410e
Diff: http://git-wip-us.apache.org/repos/asf/spark/diff/0690410e

Branch: refs/heads/branch-1.1
Commit: 0690410e4f5b34ad41146cfe2a36457394d394d8
Parents: 85e7c52
Author: Andrew Ash <and...@andrewash.com>
Authored: Wed Sep 17 15:07:57 2014 -0700
Committer: Andrew Or <andrewo...@gmail.com>
Committed: Wed Sep 17 15:08:08 2014 -0700

----------------------------------------------------------------------
 docs/spark-standalone.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/spark/blob/0690410e/docs/spark-standalone.md
----------------------------------------------------------------------
diff --git a/docs/spark-standalone.md b/docs/spark-standalone.md
index c791c81..99a8e43 100644
--- a/docs/spark-standalone.md
+++ b/docs/spark-standalone.md
@@ -307,7 +307,7 @@ tight firewall settings. For a complete list of ports to 
configure, see the
 
 By default, standalone scheduling clusters are resilient to Worker failures 
(insofar as Spark itself is resilient to losing work by moving it to other 
workers). However, the scheduler uses a Master to make scheduling decisions, 
and this (by default) creates a single point of failure: if the Master crashes, 
no new applications can be created. In order to circumvent this, we have two 
high availability schemes, detailed below.
 
-# Standby Masters with ZooKeeper
+## Standby Masters with ZooKeeper
 
 **Overview**
 
@@ -347,7 +347,7 @@ There's an important distinction to be made between 
"registering with a Master"
 
 Due to this property, new Masters can be created at any time, and the only 
thing you need to worry about is that _new_ applications and Workers can find 
it to register with in case it becomes the leader. Once registered, you're 
taken care of.
 
-# Single-Node Recovery with Local File System
+## Single-Node Recovery with Local File System
 
 **Overview**
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org

Reply via email to