[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9946 [Tor]: Bootstrapping Tor client hangs up on its chosen guards
#9946: Bootstrapping Tor client hangs up on its chosen guards
------------------------+--------------------------------
Reporter: arma | Owner:
Type: defect | Status: needs_review
Priority: normal | Milestone: Tor: 0.2.4.x-final
Component: Tor | Version:
Resolution: | Keywords: tor-client
Actual Points: | Parent ID:
Points: |
------------------------+--------------------------------
Comment (by arma):
Yes -- all the guards are marked made-contact, so we don't abandon them
when we connect to them.
That said, there are still ways to improve the situation here.
A) if one of our three guards is a bust, it will take 120 seconds for
requests to it to time out, and even if the other 2 guards are working
great, that typically isn't enough for enough to get to 80%. So there will
remain cases where we wait 2 minutes to bootstrap -- and maybe this patch
even increases the chance of those since any of the three guards can cause
them.
B) Our choice of how many microdescs to fetch per directory request is
really totally irrational since the network has grown so much since we
chose those parameters.
{{{
Oct 11 13:32:44.779 [info] launch_descriptor_downloads(): Launching 50
requests for 4574 microdescs, 92 at a time
}}}
Seriously, we're making 50 requests and spreading them over 3 guards? I
guess it's nice that we can get partial answers, but generally partial
answers don't help us.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9946#comment:11>
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