zymap opened a new issue, #22316: URL: https://github.com/apache/pulsar/issues/22316
### 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 3.1.2. It works fine on the 3.0.x ### Minimal reproduce step 1. Start up standalone 2. Adjust the ledger rollover settings to make the ledgers switch fast ``` managedLedgerMaxEntriesPerLedger=500 managedLedgerMinLedgerRolloverTimeMinutes=0 ``` 3. Set the retention policy on the namespace `public/default` ``` bin/pulsar-admin namespaces set-retention --size 0 --time 0 public/default ``` 4. Set the messageTTL on the namespace `public/default` ``` bin/pulsar-admin namespaces set-message-ttl public/default -ttl 10s ``` 5. Produce messages ``` bin/pulsar-perf produce test -r 100 ``` 6. Keep watch the stats-internal ``` bin/pulsar-admin topics stats-internal test ``` 7. Because the message expiration check interval is 5min. Set the messageTTL by admin to trigger it immediately ``` bin/pulsar-admin namespaces set-message-ttl public/default -ttl 10s ``` ### What did you expect to see? The cursor moves forward. ### What did you see instead? The cursor doesn't move. ### 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]
