Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #1863
Closed
Open
Created Aug 24, 2010 by Mike Perry@mikeperryDeveloper

Relays should store observed bandwidth in state file

arma suggested I write a proposal for this, but I believe it is a flat out bug. When a relay goes down, it looses its 24 hour observed bandwidth window. For fast relays, this can be catastropic, as it takes weeks for them to regain their bandwidth due to our slow descriptor refresh interval. The slow descriptor refresh interval can be shortened, but that requires careful study to make sure we do not increase the descriptor load on clients.

If we just instead stored this info in the state file to survive crashes, high bandwidth relays would still spend a loooong time gathering bandwidth (and maybe this is a really good thing?), but will at least not have to restart when they die.

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