I agree with @merlimat , I can see two major drawbacks with server-side implementation, which may prevent us to enable this feature with high traffic pulsar system: a. memory footprint required by producer queues b. authroization handling because publish will happen on-behalf of consumer by broker.
DLQ mainly requires count of message redelivery and then publish max-redelivered message to the DLQ. Same message can be re-delivered to different consumers so, client can't track of redelivery-count of a specific message. so, client can rely on broker to get that count and publish that message to DLQ and ack the message on original topic. I think client-side implementation can make it simpler to use this feature. [ Full content available at: https://github.com/apache/incubator-pulsar/pull/2400 ] This message was relayed via gitbox.apache.org for [email protected]
