Hi Sanjana. Thanks for the KIP! Seems quite useful not to overwhelm the brokers with the described requests from clients.
You have the votes already, and I'm also in favor overall, but I've made a couple of questions (sorry for the delay) regarding Connect, which is also using retry.backoff.ms but currently is not mentioned in the KIP, as well as a question around how we expect the new setting to work with rebalances in clients that inherit from the AbstractCoordinator (Consumer and Connect at a minimum). Maybe it's worth clarifying these points in the KIP, or the mailing list thread in case I missed something w/r/t the intent of the changes. Best, Konstantine On Tue, Mar 24, 2020 at 9:42 PM David Jacot <dja...@confluent.io> wrote: > +1 (non-binding) > > Thanks for the KIP, great improvement! > > Le mer. 25 mars 2020 à 04:44, Gwen Shapira <g...@confluent.io> a écrit : > > > +1 (binding) - thank you > > > > On Mon, Mar 23, 2020, 10:50 AM Sanjana Kaundinya <skaundi...@gmail.com> > > wrote: > > > > > Hi Everyone, > > > > > > I’d like to start a vote for KIP-580: Exponential Backoff for Kafka > > > Clients. The link to the KIP can be found here: > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-580%3A+Exponential+Backoff+for+Kafka+Clients > > > . > > > > > > Thanks, > > > Sanjana > > > > > > > > >
