New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exponential backoff in BGP reconnects #84

Closed
danderson opened this Issue Dec 16, 2017 · 0 comments

Comments

Projects
1 participant
@danderson
Copy link
Member

danderson commented Dec 16, 2017

Is this a bug report or a feature request?:

Feature request

What happened:

Right now if you're connecting to a misconfigured BGP peer, metallb retries the connection every 2s.

Most BGP implementations implement error backoff, where if the session errors out, they will blindly refuse any new connection attempts for N seconds, to avoid overloading their flimsy CPUs with broken BGP sessions.

This means that if you try connecting metallb to a misconfigured peer, the logs will show the "real" error once, followed by 1-3 minutes of "reading from peer: EOF" errors as metallb keeps retrying.

What you expected to happen:

The logs should do a better job of highlighting the real error.

@danderson danderson added this to the v0.4.0 milestone Dec 19, 2017

@danderson danderson added this to To Do in BGP mode via automation Jan 15, 2018

@danderson danderson modified the milestone: v0.4.0 Jan 16, 2018

@danderson danderson closed this in be97302 Jan 25, 2018

BGP mode automation moved this from To Do to Done Jan 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment