This is a great suggestion. I like how we just do it by default instead of making it a choice users need to figure out. Avoiding connection storms is great.
One concern. If I understand the formula for effective maximum backoff correctly, then with default maximum of 1000ms and default backoff of 100ms, the effective maximum backoff will be 450ms rather than 1000ms. This isn't exactly intuitive. I'm wondering if it makes more sense to allow "one last doubling" which may bring us slightly over the maximum, but much closer to it. I.e. have the effective maximum be in [max.backoff - backoff, max.backoff + backoff] range rather than half that. Does that make sense? Gwen On Thu, Apr 27, 2017 at 9:06 AM, Ismael Juma <ism...@juma.me.uk> wrote: > Hi all, > > Dana Powers posted a PR a while back for exponential backoff for broker > reconnect attempts. Because it adds a config, a KIP is required and Dana > seems to be busy so I posted it: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 144%3A+Exponential+backoff+for+broker+reconnect+attempts > > Please take a look. Your feedback is appreciated. > > Thanks, > Ismael > -- *Gwen Shapira* Product Manager | Confluent 650.450.2760 | @gwenshap Follow us: Twitter <https://twitter.com/ConfluentInc> | blog <http://www.confluent.io/blog>
