Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #40062
Closed (moved) (moved)
Open
Created Feb 22, 2021 by juga@jugaMaintainer

Improve the way to recover from destination web server failure

When a destination web server fails 9 times, it's disabled for 300secs before it's tried again. We continue to incrementing seconds when fails again.

If a destination fails often or there's no other (enabled) destination, that makes the measurement continue failing.

A simple way to improve this, is to don't "disable" it and just continue trying (but logging warning).

Otherwise we should review the number of times it needs to fail and the number of seconds re-trying.

Assignee
Assign to
Time tracking