Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 627
    • Issues 627
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 116
    • Merge Requests 116
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #2441

Closed
Open
Created Jan 27, 2021 by Brian Conry@bconryDeveloper

system testing does not verify expected ADB behavior when doing overmem cleaning

As introduced on #2405, BIND currently does not behave well in at least some circumstances when the ADB is overmem and performing overmem cleaning.

Presumably we added the overmem cleaning logic with the intent that BIND should continue to run and operate relatively normally when the ADB goes overmem, and that such behavior would be better than other alternatives (e.g. flushing the entire ADB as soon as the overmem condition is detected).

We have not documented our expectations for BIND's operational performance when this behavior is triggered, nor do we have any system tests that attempt to verify that BIND is continuing to behave as we expect.

Assignee
Assign to
BIND 9.19.x
Milestone
BIND 9.19.x
Assign milestone
Time tracking
None
Due date
None