Clear poison messages counter per CG after ignore/ack

[yanivbh1]

[AmreeshTyagi]

I was just testing DLQ & came to know that this issue still persist i.e. poisoned messages are not cleaned from DLQ evan after fixing consumer & acknowledging them.

I am also trying to simulate a situation when we have many thousand messages in DLQ & need to process them all in one go. Right now only 1000 messages can be processed at once, but it would be difficult if those are still in DLQ list view after processing.

I think poison counter is not the main problem here. Main problem may be the state of poison message in DLQ which is not changing & hence counter is same & messages are also visible in DLQ list. WDYT?

[idanasulin2706]

Hi @AmreeshTyagi, current behavior is indeed not best, after validating this feature with a lot of users I'm happy to share that we re-designed the DLQ behavior so that acking a message from an application will remove it from the DLQ. Not only this but also you will be able to consume the DLQ directly from your applications. Those features should be released in the near versions so stay tuned.

[AmreeshTyagi]

Thanks for the update. Sounds good. 👍🏻

[idanasulin2706]

This has been fixed in our latest version (0.4.2)