"duplicate peers for blob warning" prior to fallback on fixed peers
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
I'm experimenting with running the desktop app with less reliance on the fixed peers.
daemon_settings.yml
fixed_peer_delay: 15.0
2022-08-24 06:25:52,279 WARNING lbry.dht.protocol.iterative_find:332: misbehaving peer 135.148.27.57:4444 returned duplicate peers for blob
2022-08-24 06:25:57,369 WARNING lbry.dht.protocol.iterative_find:332: misbehaving peer 75.158.93.130:4444 returned duplicate peers for blob
2022-08-24 06:25:57,568 WARNING lbry.dht.protocol.iterative_find:332: misbehaving peer 188.61.102.68:4444 returned duplicate peers for blob
2022-08-24 06:26:08,741 WARNING lbry.dht.protocol.iterative_find:332: misbehaving peer 135.148.27.57:4444 returned duplicate peers for blob
2022-08-24 06:26:09,233 WARNING lbry.dht.protocol.iterative_find:332: misbehaving peer 75.158.93.130:4444 returned duplicate peers for blob
2022-08-24 06:26:13,888 WARNING lbry.dht.protocol.iterative_find:332: misbehaving peer 188.61.102.68:4444 returned duplicate peers for blob
It then falls back on the fixed peers and begins downloading blobs. What does this warning indicate?
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 with daemon_settings.yml and the warnings from lbry.dht.protocol.iterative_find at line 332. Trace how fixed_peer_delay: 15.0 affects fallback after duplicate peers are reported, then compare the observed behavior with the intended peer lookup flow. Done means the warning and fallback behavior are explained and any unexpected behavior is identified.
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
- Needs clarification
- Newbie friendliness
- 25/100