Gwen, Have selected priority 'minor', component as 'core', have assigned no labels. Jira link: https://issues.apache.org/jira/browse/KAFKA-3895.
I have also added a question to the jira issue, alongwith a rough approach that I have in mind. It would be great if you can have a look and provide comments. I am still setting up the dev env for kafka; will update as I progress. Thanks. -- κρισhναν On Thu, Jun 23, 2016 at 9:30 PM, Gwen Shapira <g...@confluent.io> wrote: > Thats a pretty cool feature, if anyone feels like opening a JIRA :) > > On Thu, Jun 23, 2016 at 8:46 AM, Christian Posta > <christian.po...@gmail.com> wrote: > > Sounds like something a traditional message broker (ie, ActiveMQ) would > be > > able to do with a TTL setting and expiry. Expired messages get moved to a > > DLQ. > > > > On Thu, Jun 23, 2016 at 2:45 AM, Krish <krishnan.k.i...@gmail.com> > wrote: > > > >> Hi, > >> I am trying to design a real-time application where message timeout can > be > >> as low as a minute or two (message can get stale real-fast). > >> > >> In the rare chance that the consumers lag too far behind in processing > >> messages from the broker, is there a concept of expired message queue in > >> Kafka? > >> > >> I would like to know if a message has expired and then park it in some > >> topic till as such time that a service can dequeue, process it and/or > >> investigate it. > >> > >> Thanks. > >> > >> Best, > >> Krish > >> > > > > > > > > -- > > *Christian Posta* > > twitter: @christianposta > > http://www.christianposta.com/blog > > http://fabric8.io >
