Node should automatically re-connect to DHT network
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
The Issue
For a number of reasons, a lbrynet client may disconnect from the DHT network resulting in these types of log messages:
Line 1973: 2018-06-12 09:13:59,752 WARNING lbrynet.dht.node:635: This node doesnt know any other nodes
When this occurs, the client should attempt to rebind(if needed) it's UDP/TCP ports and rejoin the network.
System Configuration
- LBRY Daemon version:
- LBRY App version:
- LBRY Installation ID:
- Operating system:
Anything Else
Screenshots
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the lbrynet.dht.node code around the warning at lbrynet.dht.node:635, and trace how the client handles having no known nodes and its UDP/TCP bindings. Verify the reconnect path against the reported log condition. Done means a disconnected client can rebind ports when needed and rejoin the DHT network automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100