merlimat closed pull request #2186: Issue 1288: Provide documentation for 
running BookKeeper auto-recovery
URL: https://github.com/apache/incubator-pulsar/pull/2186
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/deployment/terraform-ansible/templates/bookkeeper.conf 
b/deployment/terraform-ansible/templates/bookkeeper.conf
index 942dcffbbe..2f5dd4ae59 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 d23423ce71..0d6ddeeba7 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.


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to