KamenRiderKuuga opened a new issue, #21898: URL: https://github.com/apache/pulsar/issues/21898
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version pulsar running on docker: `apachepulsar/pulsar:3.1.1` ### Minimal reproduce step set the `broker.conf`: `ttlDurationDefaultInSeconds=7200` code for sending message: ```java var messageBuilder = producer.newMessage().value(payload).deliverAfter(21_600_000L, TimeUnit.MILLISECONDS); messageBuilder.sendAsync(); ``` ### What did you expect to see? The consumer received the message after 21,600,000ms(6 hours). ### What did you see instead? The message was cleared by TTL and the consumer did not receive anything. ### Anything else? On the one hand, I want to confirm whether this is the design, because this is quite counter-intuitive. We generally think that the expiration time is calculated from the delivery time of the message. If this is expected, then how can I coordinate my TTL configuration along with the sending options. ### 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]
