alexsapps opened a new issue #12053: URL: https://github.com/apache/pulsar/issues/12053
I find the [Retry letter topic](https://pulsar.apache.org/docs/en/next/concepts-messaging/#retry-letter-topic) docs confusing. Here are some questions: * Is it really the producer's responsibility to send the message to the retry topic? The docs say "you can configure the producer to send messages to both the business topic and the retry letter topic". If this is accurate, should the producer send to both topics at the same time or only push to retry topic after business topic fails? * In the code example with `.retryLetterTopic`, does the consumer get both business and retry messages in the same stream? Are retried messages delivered interleaved with business messages based on timestamps, or does the subscription prioritize one topic over the other? * What is the relationship between retryLetterTopic and enableRetry? (Is retryLetterTopic ignored when enableRetry is false? Is it an error to specify a retryLetterTopic when enableRetry is false?) * What is "retrial queue" (`reconsumeLater`) ? Is it different than a retry topic? * Is `reconsumeLater` different from throwing an exception that causes the message to go to the retryLetterTopic? * What is maxRedeliverCount – is “redeliver” different from “retry”? Is it the number of times it tries to redeliver immediately before putting it in the retry queue, or the number of times it gets put back into the retry queue before going to the dead letter topic? * The sentence starting "To configure the delay time" does not actually say how or where to specify a delay time. But I assume it is a global setting on the retry topic? -- 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]
