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

Always set lastOp to systemLastOp on no-op writes

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 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
    • 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@mongodb.com Janna Golden
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: