umialpha commented on issue #8095: URL: https://github.com/apache/pulsar/issues/8095#issuecomment-696493439
Hi @codelipenghui , thanks for your reply. I have tried ReconsumeLater feature, but it does not meet our requirements, like I said in my original post, > Second Attempt We use Pulsar ReCosume logic, but still cannot meet our requirement because every time we ReCosume a message, it actually generate a new message, when the worker finishes/fails the original message, it has no info about the new message. We could do some workaround here, e.g. when the consumer dispatches the original message, it first ReConsume it, generating a new Message, then dispatches the new message to the worker. I have done some performance test on it, which is really poor. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
