Gilthoniel opened a new issue, #23910: URL: https://github.com/apache/pulsar/issues/23910
### 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 Pulsar v4.0.2 Pulsar Go client v0.14 ### Minimal reproduce step With v4.0.2, after restarting brokers, we observe a wrong position in subscription after a seek by timestamp. The position seems to be the earliest position instead of the next message after the timestamp. Note that after downgrading to v4.0.1, the seeking position gets back to the proper one so the message after the timestamp. ### What did you expect to see? On a seek by timestamp, we expect the subscription to reset to the next message after the timestamp available in the topic. ### What did you see instead? We observe subscriptions to reset on the earliest position when we use seek by timestamp. ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
