Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 570
    • Issues 570
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 109
    • Merge requests 109
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • 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 ProjectsISC Open Source Projects
  • BINDBIND
  • Merge requests
  • !6607

Differentiate between initial and cumulative fetch limit logging

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Arаm Sаrgsyаn requested to merge aram/fetches-per-zone-improve-log-message into main Jul 22, 2022
  • Overview 3
  • Commits 1
  • Pipelines 2
  • Changes 1

Cumulative fetch limit logging happens on an event of a dropped fetch if 60 seconds have been passed since the previous log message. This change makes the log message different for the initial event and for the later cumulative events to provide more useful information to the system administrator.

Closes #3461 (closed)

Edited Aug 04, 2022 by Michał Kępień
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: aram/fetches-per-zone-improve-log-message