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
  • #7986
Closed (moved) (moved)
Open
Created Jan 17, 2013 by Nick Mathewson@nickm🥄

Lengthen the consensus validity interval

Right now, the 24 hour "build a consensus in this interval or die horribly" time is chosen completely arbitrarily. I know of no reason to not allow 48 or 72 hours.

See comments on #2681 (moved) for more discussion of this point. There's some discussion there of choosing an optimal time, but I suggest we just have some clients try 48 or 72 hours and see how it goes.

I'm boldly going with 72.

cc'ing arma because he remembers where the pain points are on the directory info download food chain, and mike because he has felt the pain.

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