-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
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.
- causes
-
SERVER-102765 Create collection can be rollbacked and not retried on a Replica Set cluster
-
- Closed
-
- is related to
-
SERVER-98461 findAndModify where query does not have shard key does not return WCE on failure
-
- Closed
-
-
SERVER-96839 Pass writeConcern from UMCs into UMCTransaction
-
- Closed
-
-
SERVER-99915 FLE2 findAndModify should also return WCE from transaction API result
-
- Closed
-
-
SERVER-102765 Create collection can be rollbacked and not retried on a Replica Set cluster
-
- Closed
-
-
SERVER-103664 Ensure Operations Are Quiesced Before Stopping Secondaries in mongos_writes_wait_for_write_concern_sharded_addl_crud_ops.js
-
- Closed
-
-
SERVER-106672 [v8.0] Add replicateSearchIndexCommand to list of all commands in write_concern_all_commands.js
-
- Needs Merge
-
-
SERVER-100936 Mongos must return WCE as a top-level error for create collection
-
- Closed
-
-
SERVER-100937 Mongos must return WCE on dropIndexes
-
- Closed
-
-
SERVER-100938 Mongos must return WCE on createIndexes
-
- Closed
-
-
SERVER-100939 Mongos should return WCE on no-op setFeatureCompatibilityVersion
-
- Closed
-
-
SERVER-100942 setDefaultRWConcernDefault must return WCE
-
- Closed
-
-
SERVER-100943 abortTransaction must wait for write concern and return WCEs on failure
-
- Closed
-
-
SERVER-101386 Test all commands that accept write concern against timeseries collections
-
- Closed
-
-
SERVER-101387 Test all commands that accept write concern against FLE collections
-
- Closed
-
-
SERVER-102312 Ensure that mongos upgrades the WC of a shardCollection request to 'majority' when possible
-
- Closed
-
-
SERVER-102571 Check against WriteConcernError category when processing QE transactions
-
- Closed
-
- related to
-
SERVER-84081 FLE2 write error hides write concern error
-
- Closed
-
-
SERVER-104220 Router must take into account drop collection write concern error
-
- Closed
-
-
SERVER-100528 Investigate all commands that accept write concern for WCE handling
-
- Closed
-
-
SERVER-104331 Perform an audit over non-sharding DDLs to ensure that they all honor the received WC parameter in case of no-op
-
- Closed
-
-
SERVER-105528 Fix FLE2 findAndModify write concern error reporting in mongod
-
- Closed
-
-
SERVER-106577 [v8.0] Prepare SPM-4070 8.0 branch for release
-
- Closed
-
-
SERVER-102571 Check against WriteConcernError category when processing QE transactions
-
- Closed
-