apache / apache/pulsar

pulsar bookkeeper.conf cannot cover all bookkeeper config property keys

Open
#16,895 3 comments 0 reactions 0 assignees View on GitHub
Stale
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

**Is your enhancement request related to a problem? Please describe.**
bookkeeper.conf in https://github.com/apache/pulsar cannot cover all keys in bk_server.conf in https://github.com/apache/bookkeeper . Starting a bookkeeper in pular archive cannot customize some bookkeeper configations by add configmap key values. For example serverNumIOThreads.

**Describe the solution you'd like**
copy all property keys in bk_server.conf to bookkeeper.conf

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

Research direction

Start by comparing Pulsar's bookkeeper.conf with BookKeeper's bk_server.conf, focusing on keys such as serverNumIOThreads and how configmap values are passed when starting BookKeeper in the Pulsar archive. Done means the relevant BookKeeper property keys are exposed in bookkeeper.conf and can be customized through configmap values.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.