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

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



#6752: TestingTorNetwork doesn't lower the dir fetch retry schedules
--------------------------------------+-------------------------------------
 Reporter:  arma                      |          Owner:                    
     Type:  enhancement               |         Status:  new               
 Priority:  major                     |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor                       |        Version:                    
 Keywords:  tor-client small-feature  |         Parent:  #7172             
   Points:                            |   Actualpoints:                    
--------------------------------------+-------------------------------------

Comment(by karsten):

 I started looking into this today, and I think we should add new config
 options, e.g., TestingClientDownloadSchedule (accepting a CSV list),
 TestingClientConsensusDownloadSchedule (accepting a CSV list), and
 TestingClientMaxIntervalWithoutRequest (accepting an INTERVAL) that can
 only be changed if TestingTorNetwork is set.  I hope to get away without
 changing all those other constants that arma changed in the diff he gave
 to Chris.  The fewer new torrc options we add, the better.  But I think
 we'll have to create separate options for these things, rather than
 magically changing timings when TestingTorNetwork is set.

 But before I write a patch, how would I reproduce the situation where
 clients don't bootstrap because of too high dir fetch retry schedules?  I
 tried a tiny-m1.large network with Tor 0.2.3.25, but scallion.log looks
 normal to me.  What log messages would I look for?  Or how would I change
 the configuration to reproduce the problem?

 With respect to the use case where people attempt to faithfully reproduce
 timing problems: we're already changing plenty of timings in
 TestingTorNetwork mode.  If this use case exists, people should manually
 reset timing-related options to non-TestingTorNetwork defaults.  Not
 directly related to this issue though.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6752#comment:15>
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