[SERVER-37343] Enable single shard transactions tests on "majority read concern off" variant Created: 27/Sep/18 Updated: 29/Oct/23 Resolved: 13/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2018-12-03, Repl 2018-12-17 |
| Participants: |
| Description |
|
Once we respect maxTargetSnapshotHistoryWindowInSeconds when enableMajorityReadConcern=false, we can enable single shard transactions tests on the "majority read concern off" variant. Until then, we would expect to get intermittent SnapshotTooOld errors. We should enable the sharded_core_txns suite and permit tests with the tag uses_single_shard_transaction. |
| Comments |
| Comment by Githook User [ 13/Dec/18 ] |
|
Author: {'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile'}Message: |