Hi Arun, Currently, the dead letter policy only worked for a shared subscription. It doesn't work for the subscriptions that have ordering implications such as "failover", "key_shared", and "exclusive".
To better understand your requirements, what are the actions when a key is moved to a dead letter queue? Does it mean all the messages with the same "key" can not be published to the original topic? How to move the "key" out of the dead letter queue? - Sijie On Wed, Mar 11, 2020 at 7:08 AM Arun Kumar <arunkumar6...@gmail.com> wrote: > Hi Team, > > I have a requirement and not sure if that is already part of Apache pulsar. > > We heavily rely on KeyShared subscriptions and need to understand if a > functionality is already available. > > Question: > If a message is in exception and moved to deadletter queue, will all the > other messages of same key will they move to deadletter or they are in > normal flow. > > In our scenario we cannot process 2nd message with key if 1st message with > same key is in exception. > > Is there a way for pulsar to auto move all the messages with that key to > deadletter rather than handling it manually? > > Thanks, > Arun >
