Apache BookKeeper - a scalable, fault tolerant and low latency storage service optimized for append-only workloads

Clone this repo:
  1. 0621ae6 Only stop Gc for the fill disk for DbLedgerStorage (#4661) by Xiangying Meng · 6 days ago master
  2. 5870922 [fix]Wrong error code(-107) of opening a deleted ledger (#4657) by fengyubiao · 7 days ago
  3. 2789316 Remove unused commons-lang dependency (#4654) by Matteo Merli · 3 weeks ago
  4. c9b893f Remove commons-configuration2 and commons-beanutils from top level dependencies (#4648) by Lari Hotari · 4 weeks ago
  5. 417ff16 add rate limit for zk read rate in gc. (#4645) by Wenzhi Feng · 4 weeks ago

Maven Central

Apache BookKeeper

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:

  • WAL (Write-Ahead-Logging), e.g. HDFS NameNode, Pravega.
  • Message Store, e.g. Apache Pulsar.
  • Offset/Cursor Store, e.g. Apache Pulsar.
  • Object/Blob Store, e.g. storing state machine snapshots.

Get Started

  • Checkout the project website.
  • Concepts: Start with the basic concepts of Apache BookKeeper. This will help you to fully understand the other parts of the documentation.
  • Follow the Installation guide to set up BookKeeper.

Documentation

Please visit the Documentation from the project website for more information.

Get In Touch

Report a Bug

For filing bugs, suggesting improvements, or requesting new features, help us out by opening a GitHub issue.

Need Help?

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.

Contributing

We feel that a welcoming open community is important and welcome contributions.

Contributing Code

  1. See our installation guide to get your local environment setup.

  2. Take a look at our open issues: GitHub Issues.

  3. Review our coding style and follow our pull requests to learn more about our conventions.

  4. Make your changes according to our contributing guide