lhotari opened a new issue, #23900: URL: https://github.com/apache/pulsar/issues/23900
### 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 any released version ### Minimal reproduce step When an entry gets added to the replay queue, it doesn't get added to the cache. The read for this entry will usually happen short after and this will result in a new read to bookkeeper. This issue will be reported separately so that it's possible to address issues individually. ### What did you expect to see? Replay queue reads should also be eligible for caching and get cached. ### What did you see instead? No caching ### Anything else? This was previously reported as part of #23504 ### Are you willing to submit a PR? - [x] 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]
