Always set lastOp to systemLastOp on no-op writes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • v8.1, v8.0, v7.0, v6.0
    • Cluster Scalability 2025-03-17
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We need to wait for write concern even on no-op writes. Today, we try to enforce doing this here, but some commands won't have taken the global write lock on the opCtx (e.g. create collection in a sharded cluster) and so will miss waiting. We should just always set the lastOp to the systemLastOp for write requests as long as we're not in a txn.

              Assignee:
              Janna Golden
              Reporter:
              Janna Golden
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: