Skip to content

Conversation

@rastislavs
Copy link
Contributor

In the existing implementation, the initial connection from GoBGP side was not attempted until the timer with a random value from the interval [5, 10) seconds expired (derived from hardcoded minConnectRetryInterval, not configurable by any way).

This change makes the initial connection attempt immediate, and lowers the minConnectRetryInterval to 1s. This helps to reduce convergence times, which is helpful especially in the datacenter deployment scenarios.

In the existing implementation, the initial connection
from GoBGP side was not attempted until the timer
with a random value from the interval [5, 10) seconds expired.

This change makes the initial connection attempt immediate,
and lowers the minConnectRetryInterval to 1s. This helps to
reduce convergence times, which is helpful especially
in the datacenter deployment scenarios.

Signed-off-by: Rastislav Szabo <[email protected]>
@fujita
Copy link
Member

fujita commented Feb 28, 2025

Supposed to be closed?

@rastislavs
Copy link
Contributor Author

Yes, closing this one in favor of #2885

Could not make the tests pass after removing the sleep before the initial connect completely, not sure if it was a test issue or I missed something else. For now #2885 is a good first step, we may look into removing the initial sleep later.

@rastislavs rastislavs closed this Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants