Now that all chunk operations run in specialized config server commands, those commands can just do their multi-doc transaction writes directly in a single WUOW, there's no need to rely on applyOps/doTxn machinery. Doing this for 4.0 would allow us to remove support for atomic applyOps in 4.0, which is something the repl team is quite interested in.
- depends on
-
SERVER-65836 Change applyOps for internal transactions in commitChunkMigration
- Closed
-
SERVER-65837 Use internal transactions instead of applyOps in removeShard
- Closed
-
SERVER-65838 Remove applyOpsDeprecated usage from split/merge chunk functions
- Closed
- is depended on by
-
SERVER-33325 review use of "b" field in applyOps update operations in sharding_catalog_manager_chunk_operations.cpp
- Closed
-
SERVER-33182 Remove atomic applyOps
- Closed
- is duplicated by
-
SERVER-53502 Consider introducing fine grained chunk locks
- Closed
- is related to
-
SERVER-58026 Omitted FTDC sections cause frequent schema changes that limit FTDC retention
- Backlog
- related to
-
SERVER-65531 Crash when running applyOps command with "needsRetryImage" option
- Backlog
-
SERVER-65774 applyOps command does not to write to config.image_collection on secondaries in some cases
- Backlog
-
SERVER-50381 3 way deadlock between applyOps cmd, prepared transaction and secondary oplog fetcher initiated find command
- Closed
-
SERVER-65553 Atomic applyOps generates a change stream pre-image on secondaries but not on the primary
- Closed
-
SERVER-64972 Generate change stream events for batched deletes
- Closed
-
SERVER-36263 Bypassing operation validation in applyOps should require special privilege
- Closed