-
Type: Bug
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding, Testing Infrastructure
-
ALL
-
Sharding 2019-02-25, Sharding 2019-03-11, Sharding 2019-03-25, Sharding 2019-04-08, Sharding 2019-04-22, Sharding 2019-05-06, Sharding 2020-04-06
-
10
If a jstest that manually runs transaction statements fails with a TransientTransaction error, it is safe to retry the whole transaction, but it currently has no way to retry the previous statements, so the test will fail unnecessarily. The suites that run core/txns tests against sharded clusters are particularly susceptible to this, because of the chance of snapshot errors on slow hosts.
Each targeted test / suite could use an override file (similar to the existing txn_override.js) that batches transaction operations and supports advancing a session's txnNumber transparently to do this. The override wouldn't have to handle network errors or failovers, just transient transaction errors.
- is duplicated by
-
SERVER-41338 Add LockTimeout as allowed error for snapshot_read_kill_op_only.js
- Closed
- is related to
-
SERVER-36310 Unblacklist transactions from all jscore passthroughs that use replica sets
- Closed
- related to
-
SERVER-46510 Concurrent drop-pending notifications can race with subsequent transactions
- Closed