-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expire command affect only one message #732
Comments
This command should be can expires all messages older than given 100 seconds for service-subscription-name of my-tenant/my-namespace/some-topic topic. Right now I checked the Pulsarctl codebase, and it seems right to me. Could you try If this command can meet your needs, we will fix the Pulsarctl. |
@nodece the command you suggested didn't meet my need - behaviour is exactly the same 🤔 At this point I'm utterly confused - you say that is should expire all messages that are beyond Do you think this might have different outcome depending on type of subscription / TTL settings? I use to to |
@zymap Could you take a look this issue? |
@worekleszczy Could you provide which you are using the Pulsar version? You can also make an issue in Pulsar. |
|
Which is the Pulsar version? |
Hi,
I'm not sure if this is a bug, but it's definitely confusing me.
Some time age I wanted to manually expire messages for a subscription - I don't have ttl set up for a topic and a service I was manually expiring messages for keep
nack
messages due to invalid format, so to prevent this from happen infinitely I run a command:Prior to that I had 40 unacked messages, but after running this I remained with 39. I ended up running this in a loop, but I expected this command to expire all messages that are past
expire time
argument. Is this the correct behavior? For a while I thought that-a
it for such use case as mine, but according to #707 it's for something else.The text was updated successfully, but these errors were encountered: