| commit | 00622bce6279ecf40fe044abe5bd7a29722b2535 | [log] [tgz] |
|---|---|---|
| author | Michael Marshall <47911938+michaeljmarshall@users.noreply.github.com> | Sun Dec 06 19:52:53 2020 -0700 |
| committer | GitHub <noreply@github.com> | Sun Dec 06 18:52:53 2020 -0800 |
| tree | 1ab0c2d1af60003109ae5a2760925db084207ec3 | |
| parent | 63b3e5a0759f05fde752cc5ade07ea19a8f2b114 [diff] |
Add Some Clarifications to the AutoRecovery Documentation Descriptions of the changes in this PR: ### Motivation I recently started using Apache Bookkeeper as part of my Apache Pulsar cluster. In learning some of the operational tasks related to managing the bookies and autorecovery, I noticed a few places where the documentation could be improved. ### Changes The changes are all to the `AutoRecovery.md` file for version 4.12.0. They might apply to earlier versions, but I'm not sure how documentation updates are handled. My first change is to explicitly mention the way to turn off the AutoRecovery daemon on the bookie nodes. This configuration was not obvious to me as a new user of the project, and I accidentally had recovery workers running on all nodes. (Regarding that, I mention in the PR that it is possible to run the process on bookie and autorecovery nodes. Perhaps this isn't an intended use case though? If that is so, it should be mentioned in the documentation.) I also added a clarification to the `disable` auto recovery documentation because it wasn't obvious to me that running the script would stop autorecovery for the whole cluster. Thanks! Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <None> This closes #2507 from michaeljmarshall/document-autorecovery-more
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
You can also read Turning Ledgers into Logs to learn how to turn ledgers into continuous log streams. If you are looking for a high level log stream API, you can checkout DistributedLog.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.