#20534: Revise hard-coded download schedules
------------------------------+--------------------------------
Reporter: teor | Owner:
Type: defect | Status: new
Priority: Medium | Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Keywords: regression
Actual Points: | Parent ID:
Points: 0.5 | Reviewer:
Sponsor: |
------------------------------+--------------------------------
We should tweak the download schedules in config.c based on what we've
learned in #20499.
These schedules should retry sooner than never:
TestingServerDownloadSchedule
TestingClientDownloadSchedule
These schedules retry at most every 2 hours, should that be higher?
TestingServerConsensusDownloadSchedule
These schedules retry at most every 12 hours, should that be higher?
lower?
TestingClientConsensusDownloadSchedule
These schedules retry at most every 73 hours, should that be lower?
Should we try more times before jumping to retrying after an hour?
ClientBootstrapConsensusAuthorityDownloadSchedule
ClientBootstrapConsensusFallbackDownloadSchedule
ClientBootstrapConsensusAuthorityOnlyDownloadSchedule
Should we try more than 7 or 8 times to get directory documents?
TestingConsensusMaxDownloadTries
ClientBootstrapConsensusMaxDownloadTries
TestingDescriptorMaxDownloadTries
TestingMicrodescMaxDownloadTries
TestingCertMaxDownloadTries
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20534>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
