rocketraman opened a new issue #5349: UnAckedMessageTracker: 3600 messages have timed-out... but they haven't? URL: https://github.com/apache/pulsar/issues/5349 **Describe the bug** I've deployed a topic into Pulsar 2.4.1 with default configuration for message TTL, which as I understand it should mean that unacked messages should be retained forever. However, my consumers periodically report: ``` org.apa.pul.cli.imp.UnAckedMessageTracker : [ConsumerBase{subscription='my-sub', consumerName='my-consumer', topic='persistent://dev/my-ns/q'}] 3600 messages have timed-out ``` I've seen this on 3 separate environments, starting the topic and associated subscriptions from scratch. Subscriptions are Shared, and configured to start at position "earliest". The value is always 3600. In all 3 environments, which have vastly different numbers of messages in the topic, the number is always 3600. In some environments I don't believe 3600 messages were even placed into the topic. This doesn't actually appear to cause any problems -- everything seems to be working normally. Its just a scary and annoying message to see. **To Reproduce** Steps to reproduce the behavior: 1. Create a topic with default settings, change retention size to -1 and retention period to 1 hour (I can't see how these settings would be relevant, but that's what my topics have). 2. Produce and consume some messages from the topic. 3. Wait until the warning is reported. **Expected behavior** No warning.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
