[SERVER-29504] Support resumeAfter behavior for shard servers Created: 07/Jun/17 Updated: 30/Oct/23 Resolved: 22/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.13 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Repl 2017-07-31, Repl 2017-08-21, Repl 2017-09-11 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
On a shard server it can be okay for the provided resumeToken to not exist in any oplog entry in certain scenarios. |
| Comments |
| Comment by Githook User [ 22/Aug/17 ] |
|
Author: {'username': 'mtrussotto', 'email': 'matthew.russotto@10gen.com', 'name': 'Matthew Russotto'}Message: |
| Comment by Spencer Brody (Inactive) [ 17/Jul/17 ] |
|
This ticket is for the mongod-only changes to support the sharding behavior for resumability. Actually making resumability work in sharding, which requires changes to mongos, is covered by |