Batch noop majority writes for authoritative placement-version configTime waits

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2026-04-27, CAR Team 2026-05-11
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Authoritative placement-version recovery step 4 (_waitForConfigTimeOrChunkVersionChange) issues a best-effort appendOplogNote per call to move the majority commit point and shorten registerWaiterForMajorityReadOpTime waits.

      Many recovery threads hitting step 4 at once can amplify load on the primary.

      Investigate deduplicating or batching these no-ops on each mongod, in the spirit of how afterClusterTime path join overlapping noop writes instead of issuing one per waiter. 

            Assignee:
            Pol Pinol
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: