Replies: 1 comment 5 replies
-
When a message is not acked, it does not block the consumer until the message is redelivered. You can check that by checking the message payload if its unique (keep in mind that what you print as payload are bytes here, not string). That is probably what you see here. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm playing with Ack/Nak functionality for streams with interest policy enabled.
My goal is to stop and remove messages which are failed to process for N times:
I've noticed, that
meta.NumDelivered
sometimes provides wrong number for deliveries.For example, if
maxDeliver == 5
, thenmeta.NumDelivered
gives numbers1, 2, 3, 1, 1
(I'm expecting1, 2, 3, 4, 5
)I see such behavior when delay between redelivery attempts (via
msg.NakWithDelay(nakDelay)
) is 1 minute or more.For 5 second delay, it seems to work correct
Please help me understand if I'm missing something?
Full snippet:
And the output is:
Beta Was this translation helpful? Give feedback.
All reactions