xixiss opened a new issue #603: URL: https://github.com/apache/pulsar-client-go/issues/603
**Is your feature request related to a problem? Please describe.** For many online business systems, various exceptions usually occur in business logic processing, so the message needs to be re-consumed, but users hope that this delay time can be controlled flexibly, so "nack" is not a good choice for this scenario. **Describe the solution you'd like** I think the "re-consume" logic can be supported by pulsar-client-go itself, it can help user to acknowledgement the last message and send the same content to another delay message with a user-specified delay time: 1. Support to provide specific retry topic and dlq topic, as well as the maximum number of retries, consumers subscribe the original topic and retry topic 2. Support the user to specify the default delay time list, and the delay time used for each retry message increases step by step 3. Support users to specify delay time for every retry message **Describe alternatives you've considered** The current user's processing method is usually to send this message to a special retry topic, because production can specify any delay, so consumers subscribe the business topic and retry topic at the same time. It is not convenient to use. **Additional context** -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
