[Bug] bookie throughput is larger than broker throughput
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Version
pulsar 2.10.4
### Minimal reproduce step
bookie throughput is larger than broker throughput in pulsar 2.10.4
### bookie monitor
max bookie throughput is 500MB/S
### broker monitor
max broker throughput is 8MB/S
### pulsar persistence config
```
"bookkeeperEnsemble" : 3,
"bookkeeperWriteQuorum" : 3,
"bookkeeperAckQuorum" : 2,
"managedLedgerMaxMarkDeleteRate" : 0.0
```
### What did you expect to see?
bookie throughput = broker throughput * 3
### What did you see instead?
bookie throughput is larger than broker throughput * 3
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
No source file, test, or entry point is identified. Start by reproducing the throughput discrepancy on Pulsar 2.10.4 using the provided BookKeeper settings, then compare the bookie and broker monitor measurements; done means explaining the difference and correcting the behavior or its reporting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100