[tahoe-lafs-trac-stream] [tahoe-lafs] #26: introducer doesn't seem to forget about old peers, or peers don't forget about old peers

[tahoe-lafs]

#26: introducer doesn't seem to forget about old peers, or peers don't forget
about old peers
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  warner
         Type:  defect   |     Status:  closed
     Priority:  major    |  Milestone:  eventually
    Component:  code-    |    Version:  0.6.0
  network                |   Keywords:  availability introducer scalability
   Resolution:  fixed    |  performance
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by warner):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 The "short term fix" has been in place successfully for 5 years now, and
 is working fine. Nodes use stable FURLs, so the only deadwood/noise is
 from nodes that have left for good. Until clients remember servers
 independently of the Introducer, occasional reboots will clear out dead
 announcements (specifically: after the node leaves, after the next
 Introducer reboot, then after the following client reboot, the client will
 no longer attempt to contact the missing node).

 When clients are modified to remember servers on their own (as part of the
 #68 distributed-introduction work), they should include some timeouts, so
 nodes that haven't been heard from in any form (gossip/introduction or
 actual connection) can be forgotten.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/26#comment:14>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage