Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #6752

Closed (moved)
(moved)
Open
Created Sep 03, 2012 by Roger Dingledine@arma

TestingTorNetwork doesn't lower the dir fetch retry schedules

https://trac.torproject.org/projects/tor/ticket/6341#comment:34 shows a lot of socks timeouts from Tor clients in a Testing Tor Network. Apparently these clients didn't get enough directory info to establish circuits, so they just fail all their application requests. The issue is apparently exacerbated by #3196 (moved) where we demanded more descriptors be present before we consider ourselves bootstrapped.

Perhaps the real problem here is that we keep the normal dir fetch retry schedules even when TestingTorNetwork is set? It looks like TestingTorNetwork makes a new consensus every 5 minutes, but client_dl_schedule is "0, 0, 60, 605, 6010, INT_MAX".

Should we lower the retry schedules?

Has it been the case this whole time that clients in testing networks typically don't have all the descriptors they'd want?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking