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
  • #18809

Closed (moved)
(moved)
Open
Created Apr 13, 2016 by teor@teor

Handle linked connections better during bootstrap

begindir connections advance directly to the CLIENT_SENDING state, even before their TLS connection is created.

So we need to modify the logic from #4483 (moved) that checks for consensuses that are downloading:

  • is it a direct connection in state after connecting, or
  • a linked connection that's attached, or
  • a linked connection that's in a state after sending

And then do the standard "extra consensus download check" when we're about to link a directory connection to a TLS connection.

Or arma may have a better idea.

I am not sure whether we should fix this in 0.2.8, because the current code works, but it's not optimal when too many TLS connections hang. Tagging it just in case.

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