[SERVER-50119] Create merged oplog buffer iterator for resharding Created: 05/Aug/20 Updated: 06/Dec/22 Resolved: 02/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | 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: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Each oplog buffer iterator represents an _id-sorted stream on the oplog buffer collection for a particular donor shard. The oplog buffer iterators for all donor shards should be merged together as a single _id-sorted stream. Consider reusing the AsyncResultsMerger or pieces of it. |
| Comments |
| Comment by Max Hirschhorn [ 02/Nov/20 ] |
|
The oplog application rules for resharding permit the oplog entries from each donor shard to be applied independently. There is no longer a need to merge the oplog buffer iterators. |