Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 524
    • Issues 524
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 100
    • Merge requests 100
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #220

Closed
Open
Created Apr 21, 2018 by Cathy Almond@cathyaDeveloper

ISC_SOCKET_MAXEVENTS is too small by default

In a couple of KB articles, we recommend increasing it if necessary. (See: https://kb.isc.org/article/AA-00508/0). When building BIND with --with-tuning=large we increase it significantly.

Enough environments encounter the error message "maximum number of FD events ... received" that we have considered increasing the default from 64 to 256 in newer versions of BIND - but have yet to do so.

Is now perhaps the time to do this?

References:

  • https://bugs.isc.org/Ticket/Display.html?id=28438
  • https://bugs.isc.org/Ticket/Display.html?id=29538
  • https://support.isc.org/Ticket/Display.html?id=4760
  • https://support.isc.org/Ticket/Display.html?id=4963
Edited Apr 24, 2018 by Michał Kępień
Assignee
Assign to
Time tracking