Search before asking

• I searched in the issues and found nothing similar.

Read release policy

• 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.

May that be related to #22129 ?

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!