You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/12/23 09:31:24 UTC

[GitHub] [pulsar] balkrishan333 created a discussion: Broker configuration for redelivery of messages

GitHub user balkrishan333 created a discussion: Broker configuration for redelivery of messages

Is there some broker configuration which can help in redeliver the messages if messages are not acknowledged in specific time. I know about the Consumer API using which I can set ackTimeout but I am looking for some configuration on broker so that it can be applied to all consumers and topics.

GitHub link: https://github.com/apache/pulsar/discussions/19042

----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org


[GitHub] [pulsar] eolivelli added a comment to the discussion: Broker configuration for redelivery of messages

Posted by GitBox <gi...@apache.org>.
GitHub user eolivelli added a comment to the discussion: Broker configuration for redelivery of messages

Until the consumer disconnects or sends a NACK the broker thinks that the message is owned by it.
Why would you want to redeliver the message?

I think that we need more a mechanism to disconnect consumers that appear stuck, and that will trigger redelivery. (Circut breaker)

Because resending messages to the same consumer will likely end in not seeing the messages processed (why should the message be processed the second time if it didn't work the first time?)


Cc @michaeljmarshall 

GitHub link: https://github.com/apache/pulsar/discussions/19042#discussioncomment-4493928

----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org