forceSyncSource helper hangs on shardsvr due to implicit majority write concern

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0, 7.0.32
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.2, v8.0, v7.0
    • CAR Team 2026-01-19
    • 200
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      After SERVER-111031, default write concern ({w: "majority"}) is now applied to shardsvr nodes. This causes forceSyncSource() in sync_source.js to hang indefinitely when called on a replica set where another secondary is already blocked by a failpoint.

      forceSyncSource() temporarily blocks its target node with stopReplProducer before inserting a document. If the caller has already blocked a different secondary, then 2 of 3 nodes cannot replicate, making majority impossible.

      We should use explicit {w: 1} for the insert in forceSyncSource(), matching the pattern already used in assertSyncSourceChangesTo() in the same file.

            Assignee:
            Meryama Nadim
            Reporter:
            Meryama Nadim
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: