Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Icecast-Server
Icecast-Server
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 93
    • Issues 93
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Xiph.Org
  • Icecast-ServerIcecast-Server
  • Issues
  • #689

Closed
Open
Opened 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
Icecast 2.3
Milestone
Icecast 2.3 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: xiph/icecast-server#689