Addnode recycle delay problematic #1874

issue darkhosis opened this issue on September 27, 2012
  1. darkhosis commented at 5:51 PM on September 27, 2012: none

    With enough IPs listed as addnodes, the default delay of 2m will cause them to cycle endlessly, never picking up other outgoing peers. With the default timeout of 5000ms, it only takes 24 addnodes timing out to keep a cycle going. I observed this with ~400 addnodes, 1000ms timeout & manually changed source to a 15m cycle time. I think it'd be nice to have the delay as a variable that could be set in the bitcoin.conf file. With a few # of addnodes, one may even want to decrease the delay time.

    Another option would be to increase the cycle time for each specific addnode by x amount per connection failure..

  2. laanwj added the label P2P on Sep 25, 2014
  3. laanwj removed the label Brainstorming on Feb 9, 2016
  4. laanwj removed the label Refactoring on Feb 9, 2016
  5. MarcoFalke commented at 8:02 PM on April 24, 2020: member

    Is this still an issue with a recent version? If yes, what are the steps to reproduce?

  6. MarcoFalke closed this on Apr 24, 2020

  7. DrahtBot locked this on Feb 15, 2022
Labels

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-29 03:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me