mirror of
https://github.com/netbirdio/netbird.git
synced 2026-08-24 16:41:30 +02:00
ce56cc6998
The relay client's reconnect backoff was built without a RandomizationFactor, so it stayed at the zero value and every client that lost the same relay server retried on the identical 2/4/8/16/32/60 second schedule, bunching up on the server as soon as it came back. Use backoff.DefaultRandomizationFactor, as the other backoffs in the client do. The mean interval is unchanged; only the per-client offset differs. The exponential backoff construction moves into newExponentialBackOff so the configuration can be asserted directly: backoff.NewTicker fires its first tick immediately, so the schedule is not observable through the ticker.