[SERVER-50118] Create oplog buffer iterator for resharding Created: 05/Aug/20 Updated: 29/Oct/23 Resolved: 01/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Randolph Tan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M2, PM-234-T-oplog-apply | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 2020-08-24, Sharding 2020-09-21, Sharding 2020-10-05 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We likely want to have the oplog buffer iterator's getNext() return a mongo::Future. A ready future would be returned when Pipeline::getNext() returns a Document. When Pipeline::getNext() returns boost::none, a future which waits until the oplog fetcher inserts another document into the oplog buffer collection, then constructs a new Pipeline, and finally returns the Document returned by calling Pipeline::getNext(). |
| Comments |
| Comment by Githook User [ 29/Sep/20 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}Message: |