Neptune-Crypto/neptune-core

mark potential peer as invalid after a few failed connection attempts

Open

#35 opened on Aug 10, 2023

View on GitHub
 (7 comments) (0 reactions) (1 assignee)Rust (45 forks)auto 404
enhancementgood first issuenetworking

Repository metrics

Stars
 (110 stars)
PR merge metrics
 (PR metrics pending)

Description

The client keeps track of potential peers by asking the peers it is currently connected to for their peers. Potential peers are kept in memory indefinitely. This leads to repeated failing connection attempts to stale peers.

Track the number of failed connection attempts per peer. If it crosses some threshold, don't attempt to connect to that peer. If the same peer gets announced again and some timeout has passed, reset the number of failed connection attempts and start connection attempts again.

Contributor guide

Research direction
Find the peer management code, add a counter for failed connection attempts per peer, and when the threshold is exceeded, skip that peer until a reset timeout passes.
Tech stack
rust
Domain
backendnetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60