When consume message fail. usually the best practice is try if after. but in different scenes, user want to re-delivery minutes after. so expect pulsar support message re-delivery delayed.
But sometimes, user can't sure that message can be consume. like a little part of system bugs. so if don't control retry times of re-delivery message, consumer will consume the problem message nonstop. so it's important to set max re-delivery times.
If message re-delivery times beyond the max re-delivery times in settings. we'd better to save messages to the dead letter queue.
So, I expect pulsar can support re-deliver message delayed, can limit max re-delivery times and beyond the max re-delivery times, messages can add into the dead letter.
When consume message fail. usually the best practice is try if after. but in different scenes, user want to re-delivery minutes after. so expect pulsar support message re-delivery delayed.
But sometimes, user can't sure that message can be consume. like a little part of system bugs. so if don't control retry times of re-delivery message, consumer will consume the problem message nonstop. so it's important to set max re-delivery times.
If message re-delivery times beyond the max re-delivery times in settings. we'd better to save messages to the dead letter queue.
So, I expect pulsar can support re-deliver message delayed, can limit max re-delivery times and beyond the max re-delivery times, messages can add into the dead letter.