mawenyu opened a new issue, #23514: URL: https://github.com/apache/pulsar/issues/23514
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### Version linux x64, java17, pulsar 3.0.4, pulsar c++ client 3.4.2 ### Minimal reproduce step 1. stop key_shared consumer 5 mininutes 2. start key_shared consumer ### What did you expect to see? 1. broker the data dispatch to consumer is closely to the the data read speed from bookie 2. consumer can finish read backlog after a couple of minutes ### What did you see instead? 1. broker read a lot of data from bookkeeper only dispatch a little the node with only broker: it‘s network receive is very big, but only transmit a little data to consumer  the node with only bookeeper: it‘s network transmit is 23Gb/s, network band with reach the hardware limit ; <img width="488" alt="Snipaste_2024-10-25_14-49-08" src="https://github.com/user-attachments/assets/4c74c4e6-9721-4529-99fd-19c4ca8052c6";> 2. consumer can not catch up; ### Anything else? the bookkeeper disk read is very low; so the data is in the bookkeeper read cache; I think maybe some bug cause pulsar broker keep read same entry from bookkeeper , cause the network bandwith exhausted ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
