Hey Ismael, Thanks for the feedback! The proposal is not to retry automatically but relies on the user polling the NetworkClient (basically, consumer.poll) to reattempt the bootstrap. If bootstrapping fails, a NetworkException (retriable) will be thrown.
Thanks! P On Thu, Feb 23, 2023 at 1:34 PM Ismael Juma <ism...@juma.me.uk> wrote: > Thanks for the KIP. Not sure if I missed it, but how long will we retry for > and when do we give up and propagate the failure to the user? > > Ismael > > On Thu, Feb 23, 2023 at 9:30 AM Philip Nee <philip...@gmail.com> wrote: > > > Hi all! > > > > I want to start a discussion thread about how we can handle client > > bootstrap failure due DNS lookup. This requires a bit of behavioral > > change, so a KIP is proposed and attached to this email. Let me know what > > you think! > > > > > > *A small remark here*: *As the title of this KIP might sound > > familiar/similar to KIP-899, it is not the same.* > > > > *In Summary:* I want to propose a KIP to change the existing bootstrap > > (upon instantiation) strategy because it is reasonable to allow clients > to > > retry > > > > *KIP: * > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-909%3A+Allow+Clients+to+Rebootstrap+Upon+Failed+DNS+Resolution > > > > Thanks! > > Philip > > >
