poorbarcode opened a new pull request, #23931:
URL: https://github.com/apache/pulsar/pull/23931
### Motivation
**Background**
- Broker assumes the entry size is `1` when no publishing after the topic
was loaded up at the latest time. Otherwise, it uses the average entries size
published during the lastest time-range of the topic loaded up.
- Issue: the average entry size is not prectice for the catch-up read
after a topic is reloaded.
- The feature `managedLedgerMaxReadsInFlightSize` assumes the entry size is
`10kb` when it read nothing. Otherwise, it uses the average entries size of the
entries read out before.
### Modifications
- Regarding the two cases above, we'd better use the average entry size of
the specific ledger
- TODO: add test
### Documentation
<!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
- [ ] `doc` <!-- Your PR contains doc changes. -->
- [ ] `doc-required` <!-- Your PR changes impact docs and you will update
later -->
- [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [ ] `doc-complete` <!-- Docs have been already added -->
### Matching PR in forked repository
PR in forked repository: x
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
