Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • 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
  • #9321
Closed (moved) (moved)
Open
Created Jul 24, 2013 by Roger Dingledine@arma

Load balance right when we have higher guard rotation periods

Here's our plan:

  1. Directory authorities need to track how much of the past n months each relay was around and had the Guard flag.
  2. They vote a percentage for each relay in their vote, and the consensus has a new keyword on the w line so clients can learn how Guardy each relay has been.
  3. Clients change their load balancing algorithm to consider how Guardy you've been, rather than just treating Guard status as binary (#8453 (moved)).
  4. Raise the guard rotation period a lot (#8240 (moved)).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking