Reset cache on message acknowledgement about rabbitmq-message-deduplication HOT 4 CLOSED

Exchange-level deduplication allow you to deduplicate based on time.
Queue-level deduplication allow you to deduplicate based on queue content. Deduplication TTL does not apply on dedup queues.

You can combine both to achieve what you are looking for. A dedup exchange will ensure duplicate messages publish within the broker will not be routed for a given amount of time. A dedup queue will prevent two equal messages to be in the same queue at the same time.

You need to consider corner cases though. For example, if your queue has plenty of elements and two equal messages come within 30 minutes from each other. Are they considered duplicates? The dedup exchange will actually route them forward as the 10 minutes TTL has already expired but the dedup queue will reject the second message as there is already one in the queue.

from rabbitmq-message-deduplication.

Hello,

the use case you describe is the one fulfilled by the queue level deduplication. A message is considered belonging to the queue up until it is not acknowledged by a consumer. Hence, if a duplicate message would arrive, it would be discarded as the consumption of the first one is still in progress.

from rabbitmq-message-deduplication.

Thanks for your quick reply @noxdafox . We just have a quick question:

If a message is sent with a TTL of 10 minutes. Worker A receives it and after 1 minute it acknowledge it. After 1 minute, the same messages comes to the queue. Will it still be deduplicated it based on TTL or it will be forward it because the previous one was acknowledge?

from rabbitmq-message-deduplication.

Thank you so much for your help!

We will change our code to acknowledge the messages and then that should be enough for us.

from rabbitmq-message-deduplication.