Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • briar briar
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 789
    • Issues 789
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • briar
  • briarbriar
  • Issues
  • #640

Closed
Open
Created Sep 05, 2016 by akwizgran@akwizgranOwner

Detect blogs that are no longer receiving updates

It's possible for a blog subscriber to be cut off from the blog's author due to upstream subscribers unsubscribing or leaving the network. We could use some combination of keepalive messages from the author and an adaptive timeout at the subscriber to detect this and mark the blog as inactive or unreachable.

If we use keepalives, the interval between keepalives should adapt to the average interval between posts. If we use a timeout at the subscriber based on the arrival times of updates, TCP's running estimates of round-trip time and round-trip time variance might be a good place to start.

Depending on the mechanism used, this might also be applicable to other kinds of group.

Assignee
Assign to
Time tracking