6f3288814c
The GetPeers requests sent while crawling the network are randomly load-balanced over available peers. But at the very beginning, they may be both routed to the same peer, causing network initialization to be delayed while the second one times out (since zcashd only ever responds to the first addr message). Only sending one GetPeers request per candidate set update means we crawl the network a little more slowly, but avoids hanging on start. |
||
|---|---|---|
| .. | ||
| peer | ||
| peer_set | ||
| protocol | ||
| address_book.rs | ||
| config.rs | ||
| constants.rs | ||
| isolated.rs | ||
| lib.rs | ||
| meta_addr.rs | ||
| peer.rs | ||
| peer_set.rs | ||
| policies.rs | ||
| protocol.rs | ||
| timestamp_collector.rs | ||