lhotari commented on code in PR #1138: URL: https://github.com/apache/pulsar-site/pull/1138#discussion_r3180382224
########## docs/administration-autorecovery.md: ########## @@ -0,0 +1,143 @@ +--- +id: administration-autorecovery +title: BookKeeper AutoRecovery +sidebar_label: "BookKeeper AutoRecovery" +description: Learn how BookKeeper AutoRecovery works in Pulsar, and how to configure, enable, disable, and monitor it. +--- + +When a bookie in a Pulsar cluster becomes unavailable, the ledgers it stored become under-replicated, meaning the data no longer meets the configured replication factor. BookKeeper provides **AutoRecovery** to detect this situation automatically and rereplicate affected ledgers to healthy bookies — without manual intervention. + +## How AutoRecovery works + +AutoRecovery runs as two concurrent components within the `autorecovery` process: + +### Auditor + +The **Auditor** is a singleton node, elected via ZooKeeper leader election from all nodes participating in AutoRecovery. When a bookie fails or is reported unavailable, the Auditor: Review Comment: In Pulsar, the solution isn't coupled with ZooKeeper. Pulsar contains Metadata store drivers for BookKeeper and it's possible to use Oxia together with BookKeeper. A lot of the Pulsar documentation doesn't yet reflect this fact. Since this is a new document, it would be useful to take the Metadata store abstract layer into account. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
