[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #6752 [Tor Client]: TestingTorNetwork doesn't lower the dir fetch retry schedules

#6752: TestingTorNetwork doesn't lower the dir fetch retry schedules
------------------------+---------------------------------------------------
 Reporter:  arma        |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  major       |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
 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 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, 60*5, 60*10, 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?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6752>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs