spark-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From andrewo...@apache.org
Subject git commit: Docs: move HA subsections to a deeper indentation level
Date Wed, 17 Sep 2014 22:08:00 GMT
Repository: spark
Updated Branches:
  refs/heads/master 5044e4953 -> b3830b28f


Docs: move HA subsections to a deeper indentation level

Makes the table of contents read better

Author: Andrew Ash <andrew@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


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

Branch: refs/heads/master
Commit: b3830b28f8a70224d87c89d8491c514c4c191d23
Parents: 5044e49
Author: Andrew Ash <andrew@andrewash.com>
Authored: Wed Sep 17 15:07:57 2014 -0700
Committer: Andrew Or <andrewor14@gmail.com>
Committed: Wed Sep 17 15:07:57 2014 -0700

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


http://git-wip-us.apache.org/repos/asf/spark/blob/b3830b28/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-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org


Mime
View raw message