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

fsync.js is non-deterministic due to ticket exhaustion

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.13
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.0, v7.0
    • CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19
    • 200
    • 2

      fsync.js expects 2 operations to be shown as "waitingForLock". However, if all tickets are exhausted, it's possible that one of the inserts will hang trying to acquire a ticket. In which case, it will never record it is waiting on a lock.

      This is more likely in versions (7.0+) since execution control can dynamically reduce the number of available write/read tickets to 4.

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: