[DISCUSS] Optimizing the Method of Estimating Message Backlog Size in Pulsar

Dear Pulsar Community, I would like to initiate a discussion regarding the optimization of the method used for estimating the message backlog size. In the current implementation, the backlog size is estimated from the mark delete position to the last confirm position, whereas the backlog message

Re: [VOTE] PIP-344: Correct the behavior of the public API pulsarClient.getPartitionsForTopic(topicName)

Hi Penghui > It's better to list the names of the 3 bindings. Thanks for reminding me. Close the vote with 3 bindings and 2 no-bindings. - Penghui Li (binding) - Yunze Xu (binding) - Jiwei Guo (binding) - Zike Yang (no-binding) - Aloys Zhang (no-binding) Thanks Yubiao Feng On Mon, Mar 25, 202

Re: [DISCUSS] cherry-pick #21816 resolving the metrics missing issue for time-based backlog

> I believe having it in the release branches is worth it. Agree with you. Thanks Yubiao Feng On Tue, Mar 26, 2024 at 9:28 AM PengHui Li wrote: > Hi all, > > I want to start a discussion to cherry-pick #21816[0] to release branches. > This PR added the metrics for the time-based backlog, which