Revisit solution to configure Bookkeeper RocksDB settings using individual RocksDB config files#583
Merged
Conversation
…o individual config files
lhotari
force-pushed
the
lh-prefer-rocksdb-config-files
branch
from
March 4, 2025 11:36
57a9340 to
031950c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Follow-up on #580
Pulsar has provided individual RocksDB config files to configure BookKeeper's RocksDB databases.
However, this configuration hasn't been consistently used since Pulsar's bookkeeper.conf doesn't contain
defaultRocksdbConf,entryLocationRocksdbConfandledgerMetadataRocksdbConfkeys.Related BookKeeper changes:
Related Pulsar changes:
Modifications
bin/update-rocksdb-conf-from-env.pyscript to applydbStorage_rocksDB_*environment variables to update the config filesVerifying this change