-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
Cluster Scalability 2025-03-17
-
200
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.
- is related to
-
SERVER-102312 Ensure that mongos upgrades the WC of a shardCollection request to 'majority' when possible
-
- In Code Review
-