Google Git
Sign in
apache / bookkeeper / 73e22cacf705e8462d80f477a0974db1d2bcf5b8
commit73e22cacf705e8462d80f477a0974db1d2bcf5b8[log] [tgz]
authorDon Inghram <don.inghram@gmail.com>Sun May 09 14:58:42 2021 -0600
committerGitHub <noreply@github.com>Sun May 09 13:58:42 2021 -0700
tree9e064aea6777d63c5e00d6b1288119b8c1fb6532
parent034ef8566ad037937a4d58a28f70631175744f53 [diff]
ISSUE2620: RocksDB log path configurable

RocksDB configuration now allows a new value "dbStorage_rocksDB_logPath"
which allows the log files to be separated from the data storage. When
not set, Bookkeeper has no change in behavior.

Descriptions of the changes in this PR:



### Motivation

(Explain: why you're making that change, what is the problem you're trying to solve)

### Changes

(Describe: what changes you have made)

Master Issue: #<master-issue-number>



Reviewers: Enrico Olivelli <eolivelli@gmail.com>, lipenghui <penghui@apache.org>, Matteo Merli <mmerli@apache.org>

This closes #2698 from dinghram/RocksDBLogPath and squashes the following commits:

bd8e212e9 [Don Inghram] Issue2620-RocksDB log path configurable: conf
eeba05291 [Don Inghram] Issue2620-RocksDB log path configurable
8 files changed
tree: 9e064aea6777d63c5e00d6b1288119b8c1fb6532
  1. .github/
  2. .test-infra/
  3. bin/
  4. bookkeeper-benchmark/
  5. bookkeeper-common/
  6. bookkeeper-common-allocator/
  7. bookkeeper-dist/
  8. bookkeeper-http/
  9. bookkeeper-proto/
  10. bookkeeper-server/
  11. bookkeeper-stats/
  12. bookkeeper-stats-providers/
  13. buildtools/
  14. circe-checksum/
  15. conf/
  16. cpu-affinity/
  17. deploy/
  18. dev/
  19. docker/
  20. gradle/
  21. metadata-drivers/
  22. microbenchmarks/
  23. shaded/
  24. site/
  25. site2/
  26. stats/
  27. stream/
  28. tests/
  29. tools/
  30. .gitignore
  31. build.gradle
  32. dependencies.gradle
  33. gradle.properties
  34. gradlew
  35. gradlew.bat
  36. Jenkinsfile
  37. LICENSE
  38. NOTICE
  39. pom.xml
  40. README.md
  41. settings.gradle
  42. version.gradle
README.md

Build Status Build Status Coverage Status 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.
  • 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 Install guide to setup 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 or opening an Apache jira.

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 Developer Setup to get your local environment setup.

  2. Take a look at our open issues: JIRA Issues Github Issues.

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

  4. Make your changes according to our contribution guide.

Improving Website and Documentation

  1. See Building the website and documentation on how to build the website and documentation.