ahuang98 opened a new pull request, #19658: URL: https://github.com/apache/kafka/pull/19658
After a small number of retries, it will become statistically likely that the exponential backoff returned by binaryExponentialElectionBackoffMs gets stuck at quorumConfig.electionBackoffMaxMs which has no jitter in it. This change lowers `RETRY_BACKOFF_BASE_MS` to 50ms from 100ms and uses this as jitter for the configurable electionBackoffMaxMs. Basically, with retries=1, the returned backoff is 50ms, but after that the returned backoff has increasing randomness and likelihood to be larger until the first calculation exceeds the configured electionBackoffMaxMs + jitter. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
