When the primary shard returns ok:1 to the router upon a drop collection command, due to SERVER-97754 it is guaranteed that the drop has been majority acknowledged.
However - since the DDL coordinator writes using a separate operation context - when the shard command returns it waits for the last op time to get majority committed (SERVER-102024). The last op time may be ahead of the drop op time.
It follows that - when the additional wait fails - a write concern error gets attached to the reply even though the drop succeeded and was majority committed. When that happens, the router will fail to parse the shard reply because the DropReply does not include a writeConcernError field.
SERVER-103506 should solve the problem for all command replies. But we should provide a temporary solution as long as the generic fix is not in.
- 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-97754 User-provided write concern is not honored for DDL operations on sharded clusters (always w:majority)
-
- Needs Scheduling
-
-
SERVER-103506 Add a generic way to return a writeConcernErrors field from TypedCommands
-
- Open
-
-
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-100942 setDefaultRWConcernDefault must return WCE
-
- Closed
-
-
SERVER-102024 Always set lastOp to systemLastOp on no-op writes
-
- Closed
-
- related to
-
SERVER-98461 findAndModify where query does not have shard key does not return WCE on failure
-
- Closed
-
-
SERVER-84081 FLE2 write error hides write concern error
-
- 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-106162 [test-only] Reevaluate ignoring write concern errors in drop FSM state
-
- Open
-
-
SERVER-106577 [v8.0] Prepare SPM-4070 8.0 branch for release
-
- Open
-
-
SERVER-106672 [v8.0] Add replicateSearchIndexCommand to list of all commands in write_concern_all_commands.js
-
- Needs Merge
-
-
SERVER-100528 Investigate all commands that accept write concern for WCE handling
-
- Closed
-
-
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-105528 Fix FLE2 findAndModify write concern error reporting in mongod
-
- Closed
-
-
SERVER-102571 Check against WriteConcernError category when processing QE transactions
-
- Closed
-