[SERVER-33989] Add support for afterClusterTime for snapshot reads through mongos Created: 19/Mar/18 Updated: 29/Oct/23 Resolved: 13/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-04-09, Sharding 2018-04-23 |
| Participants: |
| Description |
|
When choosing an atClusterTime to send to shards, mongos should check if the request had an afterClusterTime, and if it does, choose an atClusterTime >= afterClusterTime. This applies to each command that supports both readConcern afterClusterTime and readConcern snapshot. |
| Comments |
| Comment by Githook User [ 13/Apr/18 ] |
|
Author: {'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}Message: |