Thanks. Any possible reasons why we didnt made consumers partition aware. do we have a similar property for consumers.
I found that in streams application, if i increase partitions i need to restart my stream application, same would hold for consumers as well. -Sameer. On Fri, Aug 4, 2017 at 8:22 PM, Hans Jespersen <h...@confluent.io> wrote: > See the producer param called metadata.max.age.ms which is "The period of > time in milliseconds after which we force a refresh of metadata even if we > haven't seen any partition leadership changes to proactively discover any > new brokers or partitions." > > -hans > > > On Aug 4, 2017, at 5:17 AM, Sameer Kumar <sam.kum.w...@gmail.com> wrote: > > > > According to Kafka docs, producer decides on which partition the data > shall > > reside. I am aware that neither broker nor producer needs to be restarted > > to detect added partitions. > > > > Would like to understand if there is some frequency through which > producer > > detects new partitions. > > > > Though consumers were not made partiton aware, any possible reasons for > the > > same. > > > > -Sameer. >