search

apache / pulsar

Apache Pulsar - distributed pub-sub messaging system
https://pulsar.apache.org/
Apache License 2.0
14.3k stars 3.6k forks source link

inconsistent behavior in ttl strategy #16114

Open leizhiyuan opened 2 years ago

leizhiyuan commented 2 years ago

Is your enhancement request related to a problem? Please describe. A clear and concise description of what the enhancement is.

inconsistent behavior in ttl strategy，

image

if we have a sub in which msgbacklog is 1， we set retention is 24h, msgbacklog is smaller than 1000,

if one message can not be acked (the client can not process it ), there will be a message hole, but after 24h, we can not expire this message,we will do this in 24*1.5 hours. but after then, backlogsize has exceeded (with the produce_exception to client,)

user can not understand why , it is confused. I set retention to 24h, if you do this , we will be ok

Describe the solution you'd like A clear and concise description of what you want to happen.

maybe we do not need the judgment, if TTL expired , we just expire them.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

github-actions[bot] commented 2 years ago

The issue had no activity for 30 days, mark with Stale label.