Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Icecast-Server Icecast-Server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 103
    • Issues 103
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Xiph.OrgXiph.Org
  • Icecast-ServerIcecast-Server
  • Issues
  • #689
Closed
Open
Issue created Jul 26, 2005 by Gitlab Bot@GitlabBotDeveloper

YP updates should be serialised per YP directory to isolate problem servers

YP updates (touches) for all mounts and YP directories are performed in series. If a YP server is slow to respond, e.g. 10 seconds, this may cause YP listings to not be maintained properly. E.g., 36 mounts with an average response time of 10 seconds per update will take 6 minutes per update cycle, while the YP directory may expect updates every two to five minutes. All of the YP directories will be affected by one slow YP directory in the configuration.

YP servers should be isolated, with YP updates for multiple YP directories performed in parallel (a separate series for each YP server).

Assignee
Assign to
Time tracking