[SERVER-76506] Integrate ReshardingOplogApplier to MovePrimaryRecipient Created: 25/Apr/23 Updated: 24/May/23 Resolved: 24/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Brett Nawrocki | Assignee: | Abdul Qadeer |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding NYC
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
If the onlineMovePrimary feature flag is on, begin applying oplogs that were fetched by the fetcher. Write unit tests if possible to ensure that the integratation works (e.g. oplogs are applied or even simply the metrics are incremented). The ReshardingOplogApplier is somewhat monolithic in that it is an interface in front of multiple classes (e.g. iterator, batcher, applier, application rules). If it's not as simple as standing up this class as-is and having it work (i.e. changes must be made to each of those components individually), then break this ticket into subtasks as necessary. |