diff options
| author | Dongjoon Hyun <dongjoon@apache.org> | 2016-02-22 09:52:07 +0000 |
|---|---|---|
| committer | Sean Owen <sowen@cloudera.com> | 2016-02-22 09:52:07 +0000 |
| commit | 024482bf51e8158eed08a7dc0758f585baf86e1f (patch) | |
| tree | e51f2c53b027178bb4e485d2781e266d96ff6e3d /docs/spark-standalone.md | |
| parent | 1b144455b620861d8cc790d3fc69902717f14524 (diff) | |
| download | spark-024482bf51e8158eed08a7dc0758f585baf86e1f.tar.gz spark-024482bf51e8158eed08a7dc0758f585baf86e1f.tar.bz2 spark-024482bf51e8158eed08a7dc0758f585baf86e1f.zip | |
[MINOR][DOCS] Fix all typos in markdown files of `doc` and similar patterns in other comments
## What changes were proposed in this pull request?
This PR tries to fix all typos in all markdown files under `docs` module,
and fixes similar typos in other comments, too.
## How was the this patch tested?
manual tests.
Author: Dongjoon Hyun <dongjoon@apache.org>
Closes #11300 from dongjoon-hyun/minor_fix_typos.
Diffstat (limited to 'docs/spark-standalone.md')
| -rw-r--r-- | docs/spark-standalone.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/spark-standalone.md b/docs/spark-standalone.md index 3de72bc016..fd94c34d16 100644 --- a/docs/spark-standalone.md +++ b/docs/spark-standalone.md @@ -335,7 +335,7 @@ By default, standalone scheduling clusters are resilient to Worker failures (ins **Overview** -Utilizing ZooKeeper to provide leader election and some state storage, you can launch multiple Masters in your cluster connected to the same ZooKeeper instance. One will be elected "leader" and the others will remain in standby mode. If the current leader dies, another Master will be elected, recover the old Master's state, and then resume scheduling. The entire recovery process (from the time the the first leader goes down) should take between 1 and 2 minutes. Note that this delay only affects scheduling _new_ applications -- applications that were already running during Master failover are unaffected. +Utilizing ZooKeeper to provide leader election and some state storage, you can launch multiple Masters in your cluster connected to the same ZooKeeper instance. One will be elected "leader" and the others will remain in standby mode. If the current leader dies, another Master will be elected, recover the old Master's state, and then resume scheduling. The entire recovery process (from the time the first leader goes down) should take between 1 and 2 minutes. Note that this delay only affects scheduling _new_ applications -- applications that were already running during Master failover are unaffected. Learn more about getting started with ZooKeeper [here](http://zookeeper.apache.org/doc/trunk/zookeeperStarted.html). |