Need max redelivery count at message level.

[Raunak-Agrawal]

I am trying to implement retries at the message level. Depending on the type of message ( which is failed due to some exceptions) , I want to have different retry policy. Like some messages will have exponential retry with max retries count of 10. While some messages will have constant retry with retries happening till 12pm midnight. It could also be for eg. Depending on type of exception, I want to retry it differently.

I am trying to use reconsumeLater() to do this. But I am not sure how to set maxRedelivery at message level. Because from the docs, I can see, it needs to be set at consumer level. If we set at consumer level, all messages will inherit the same configuration.

I am also expecting after the retries are exhausted, messages move to the DLQ.

Can anyone help me on how can I build such retry policy and attach to message.

[Raunak-Agrawal]

Can someone please help me with this? @michaeljmarshall

[Jason918]

We don't have maxRedelivery at message level. Currently, you can get reconsumed times of a message from its properties with key RetryMessageUtil.SYSTEM_PROPERTY_RECONSUMETIMES ("RECONSUMETIMES"), and then decide whether call reconsumeLater().

I am also expecting after the retries are exhausted, messages move to the DLQ.

As for DLQ, it's basically a normal topic. You can create your own, and send messages using your own producer.

[raunakagrawal47]

@Jason918 @michaeljmarshall facing below issue: #12021

I am trying to produce 10 messages at a time. And all these 10 messages should be getting retried 'x' number of times by 1 consumer. ('x' varies at message level). But it errors out and is not able to retry.
The error message says: Need Non-Null value for key. How can we resolve it?

[Jason918]

This issue is not verified on the latest pulsar version.
Which pulsar version are you using?

[raunakagrawal47]

We are using broker (server) version 2.8 and pulsar-client version on the java application 2.10.0

[Jason918]

I suggest you can open an issue to describe this issue with more details, including broker version 2.8.x?, sample code to reproduce this.

[raunakagrawal47]

The issue got resolved. I upgraded it to 2.10.1 (the latest version) And basically, the issue was, I was setting some custom properties which had a key and a value, but the value was null, so it was not able to process. Thanks for the help @Jason918 :)