Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-81318

The TimestampMonitor should be high priority and not take tickets

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0, 7.0.3, 6.0.16
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v7.1, v7.0, v6.0
    • Execution NAMR Team 2023-10-02
    • 40

      As of SERVER-79982, the TimestampMonitor is taking flow control tickets and storage engine tickets every iteration. Previously, it would only take tickets when dropping idents. Since this is an important background cleanup task, we should exempt it from taking tickets.

      Nothing should be depending on the TimestampMonitor to free its resources, but being forced to take tickets could delay freeing up disk space longer than necessary.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: