Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

don't reconnect to ourself #1318

Merged
merged 1 commit into from
Aug 18, 2015
Merged

Conversation

rade
Copy link
Member

@rade rade commented Aug 17, 2015

When we discover that a connection target address leads to ourself we set the retry time to the zero time.Time value - the only special time.Time value. We use that marker to a) suppress subsequent
connection attempts, and b) display the next retry as 'never' in weave status|report.

Closes #1305.

When we discover that a connection target address leads to ourself we
set the retry time to the zero time.Time value - the only special
time.Time value. We use that marker to a) suppress subsequent
connection attempts, and b) display the next retry as 'never' in
`weave status|report`.

Closes #1305.
@rade
Copy link
Member Author

rade commented Aug 18, 2015

I decided against introducing another connection state because the five we have is too many already. The downside is that, as is the case now, in the summary information displayed by weave status one cannot tell the difference between connections that failed because they are self connections, and those that failed for a different reason.

We could exclude these failed self connections altogether from weave status connections and the count in weave status but that would make it impossible for users to discover that they have accidentally supplied a self address.

bboreham added a commit that referenced this pull request Aug 18, 2015
@bboreham bboreham merged commit 0b4e8b8 into master Aug 18, 2015
@rade rade deleted the 1305_suppress_self_reconnection branch August 19, 2015 20:32
@rade rade modified the milestone: 1.1.0 Aug 29, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants