Hello Brian, Could you elaborate a bit more on this sentence: "This logic can be made more intelligent by managing the expiry from when the topic was last used, enabling the expiry duration to be reduced to improve cases where a large number of topics are touched intermittently." Not sure I fully understand the proposal.
Also since now this KIP did not make any public API changes and the behavioral changes are not considered a public API contract (i.e. how we maintain the topic metadata in producer cache is never committed to users), I wonder if we still need a KIP for the proposed change any more? Guozhang On Thu, Nov 7, 2019 at 12:43 PM Brian Byrne <bby...@confluent.io> wrote: > Hello all, > > I'd like to propose a vote for a producer change to improve producer > behavior when dealing with a large number of topics, in part by reducing > the amount of metadata fetching performed. > > The full KIP is provided here: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-526%3A+Reduce+Producer+Metadata+Lookups+for+Large+Number+of+Topics > > And the discussion thread: > > https://lists.apache.org/thread.html/b2f8f830ef04587144cf0840c7d4811bbf0a14f3c459723dbc5acf9e@%3Cdev.kafka.apache.org%3E > > Thanks, > Brian > -- -- Guozhang
