lhotari commented on issue #23910: URL: https://github.com/apache/pulsar/issues/23910#issuecomment-2623862571
> [@lhotari](https://github.com/lhotari) thanks, it indeed works properly with v4.0.2 when using `-1` so that should confirm the change has introduced a regression. Thanks for confirming. I have updated the release notes with information about this regression and how to apply the workaround: https://github.com/apache/pulsar/releases/tag/v4.0.2 . It will soon be published in https://pulsar.apache.org/release-notes/versioned/pulsar-4.0.2/ . > ### Known Major Issues in this Release > > This release contains a known issue impacting the `seek` method by timestamp. This issue was reported after the release was published. > > - [Bug] Seeking by timestamp causes the subscription to reset to the earliest position ([#23910](https://github.com/apache/pulsar/issues/23910)) > > Workaround for the issue: > > The issue is caused by changes introduced in [#22792](https://github.com/apache/pulsar/pull/22792). To resolve this, disable the functionality by setting the following configuration: > > ```properties > managedLedgerCursorResetLedgerCloseTimestampMaxClockSkewMillis=-1 > ``` > > Workaround Configuration Notes: > > - This configuration key needs to be manually added to your `broker.conf` file as it doesn't exist by default > - For Apache Pulsar Helm Chart Kubernetes deployments, add the following to your values.yaml file under the `broker`/`configData` section: > > ```yaml > broker: > configData: > PULSAR_PREFIX_managedLedgerCursorResetLedgerCloseTimestampMaxClockSkewMillis: "-1" > ``` -- 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]
