Opened 14 years ago

Last modified 7 years ago

#277 closed defect (Fixed)

Fetch networkstatuses scalably

Reported by: arma Owned by:
Priority: Low Milestone: 0.1.1.x-final
Component: Core Tor/Tor Version: 0.1.1.16-rc
Severity: Keywords:
Cc: arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Right now we try to fetch the minimum number of networkstatus pages that
would make us happy. If one fails, we wait a minute before trying just
enough again. We should do something smarter, for example, fetching
more originally, and retrying immediately to fetch another pile if too
many fail from the first attempt.

Along with this, we need to audit all the places in the code where we
require a threshold of networkstatuses to claim something. I believe we
have fencepost errors all over. And in some places we still use constants
that assume there are always 3 networkstatuses in the network. Lastly, we
should make sure that an independent Tor network can still function if it
has only one authdirserver.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (2)

comment:1 Changed 14 years ago by arma

flyspray2trac: bug closed.

comment:2 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.