This is an automated email from the ASF dual-hosted git repository.
mmerli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new fd7b32c Issue 1288: Provide documentation for running BookKeeper
auto-recovery (#2186)
fd7b32c is described below
commit fd7b32c6ed4d8fd814c90718c143fcb7818c11e8
Author: Sijie Guo <[email protected]>
AuthorDate: Tue Jul 17 20:47:27 2018 -0700
Issue 1288: Provide documentation for running BookKeeper auto-recovery
(#2186)
* Issue 1288: Provide documentation for running BookKeeper auto-recovery
### Motivation
Fixes #1288. We mentioned auto-recovery in DCOS deployment. but we don't
have any instructions to run auto-recovery in bare-mental deployment.
### Changes
Update the documentation in bare-mental deployment.
* Enable autorecovery for ansible
---
deployment/terraform-ansible/templates/bookkeeper.conf | 2 +-
site/docs/latest/deployment/cluster.md | 4 ++++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/deployment/terraform-ansible/templates/bookkeeper.conf
b/deployment/terraform-ansible/templates/bookkeeper.conf
index 942dcff..2f5dd4a 100644
--- a/deployment/terraform-ansible/templates/bookkeeper.conf
+++ b/deployment/terraform-ansible/templates/bookkeeper.conf
@@ -232,7 +232,7 @@ rereplicationEntryBatchSize=5000
# openLedgerRereplicationGracePeriod=30
# Whether the bookie itself can start auto-recovery service also or not
-# autoRecoveryDaemonEnabled=false
+autoRecoveryDaemonEnabled=true
# How long to wait, in seconds, before starting auto recovery of a lost bookie
# lostBookieRecoveryDelay=0
diff --git a/site/docs/latest/deployment/cluster.md
b/site/docs/latest/deployment/cluster.md
index d23423c..0d6ddee 100644
--- a/site/docs/latest/deployment/cluster.md
+++ b/site/docs/latest/deployment/cluster.md
@@ -195,6 +195,10 @@ $ bin/bookkeeper shell bookiesanity
This will create an ephemeral BookKeeper {% popover ledger %} on the local
bookie, write a few entries, read them back, and finally delete the ledger.
+Starting from Pulsar 2.1 release, Bookies start
[AutoRecovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/)
daemons by default. Those AutoRecovery daemons will monitor the healthy of the
bookkeeper cluster and automatically re-replicate entries for those
under-replicated ledgers.
+Since `AutoRecovery` deamons are stateless processes, if you would like to run
`AutoRecovery` as a separate service, you can also disable `AutoRecovery` on
bookies by setting `autoRecoveryDaemonEnabled` to `false` in your
`bookkeeper.conf` file. And you can follow the instructions in
+[bookkeeper
documentation](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) to
run `AutoRecovery` as separate processes.
+
## Deploying Pulsar brokers
Pulsar {% popover brokers %} are the last thing you need to deploy in your
Pulsar cluster. Brokers handle Pulsar messages and provide Pulsar's
administrative interface. We recommend running **3 brokers**, one for each
machine that's already running a BookKeeper bookie.
