[SERVER-36049] Enable snapshot readConcern on mongos without atClusterTime Created: 10/Jul/18 Updated: 29/Oct/23 Resolved: 13/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:RouterSupport | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2018-07-16 | ||||
| Participants: | |||||
| Linked BF Score: | 18 | ||||
| Description |
|
To enable running tests in the core transactions suite that use snapshot readConcern against unsharded collections on a single shard, mongos needs to allow snapshot readConcern for more commands than it currently does. These commands do not need atClusterTime, since snapshot readConcern will currently only be used against a single shard and will not need to establish a global timestamp. The commands are:
|
| Comments |
| Comment by Githook User [ 13/Jul/18 ] |
|
Author: {'username': 'jsmulrow', 'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |