-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Sharding, Testing Infrastructure
-
Fully Compatible
-
Repl 2019-01-28, Repl 2019-02-11, Repl 2019-02-25, Repl 2019-03-11
-
7
txn_override.js is very difficult to get right. It will be much easier to fix and maintain it if we create tests for the override itself.
- is depended on by
-
SERVER-38937 Unify txn_override.js and auto_retry_on_network_error.js
- Closed
- is related to
-
SERVER-39360 assert.commandWorked with writeError sets error code to object
- Backlog
-
SERVER-38856 txn_override.js should not rerun every operation in the ops buffer after collection creation
- Closed
-
SERVER-38857 txn_override.js shouldn't have a write concern when creating a collection outside of a transaction
- Closed
- related to
-
SERVER-38347 txn_override.js needs to retry on NotMaster errors on implicit collection creation
- Closed
-
SERVER-38777 createCollection should not return ok: 1 with write concern errors
- Closed
-
SERVER-38778 Improve error handling on implicit collection creation in txn_override.js
- Closed
-
SERVER-39117 Must deep-copy objects in ops array in txn_override.js
- Closed
-
SERVER-36311 Add stepdowns, shutdowns, and crashes to replica_sets_multi_stmt_txn_jscore_passthrough.yml
- Closed
-
SERVER-38570 txn_override.js should also abort when writeError is not empty
- Closed
-
SERVER-38590 Allow suites using txn_override.js to run transactions without causal consistency
- Closed
-
SERVER-38215 consider making txn_override.js also retry transaction after getting a TransientTransactionError errorLabel
- Closed