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

Closed (moved)
(moved)
Open
Created Feb 14, 2013 by Nick Mathewson@nickm🍬

Clients can go crazy when unable to find directory guards

When every possible node seems down, clients appear to go crazy adding the same nodes as guards over and over. I am betting that this is due to the new directory guard code.

I have a fix for this (in need of review) in branch "no_dup_guards" in my public repository.

Found while testing different failure modes with Chutney.

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