[I] [Bug] bookie throughput is larger than broker throughput [pulsar]

["chrisxrepo (via GitHub)" <gi...@apache.org>]

chrisxrepo opened a new issue, #21446:
URL: https://github.com/apache/pulsar/issues/21446

   ### 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
   <img width="1831" alt="image" src="https://github.com/apache/pulsar/assets/7782939/d9ef987c-c98e-4f93-9d1e-a29241fda121">
   
   
   ### broker monitor
   <img width="1831" alt="image" src="https://github.com/apache/pulsar/assets/7782939/b05d38f0-ec85-4afe-b136-3eed0bf7857a">
   
   ###  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!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Bug] bookie throughput is larger than broker throughput [pulsar]

["merlimat (via GitHub)" <gi...@apache.org>]

merlimat commented on issue #21446:
URL: https://github.com/apache/pulsar/issues/21446#issuecomment-6381716174

   Thanks @chrisxrepo for the report. To check this we'd need more detail:
   - a reproduction on a currently supported release (4.0.x, 4.2.x or 5.0.x);
   - the exact metric names behind both graphs, for example bookie disk write bytes versus `pulsar_throughput_in`;
   - whether the bookie number includes reads (catch-up/backlog consumers);
   - your bookkeeper.conf (ledger storage, GC/compaction settings);
   - the broker's `managedLedger*` settings.
   
   Bookie I/O also counts journal and entry-log writes, index writes, compaction and reads, so it is usually more than 3 x the broker's ingress. If there's no update, this issue will be closed in a few weeks.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org