[SERVER-51741] Preemptively schedule next batch in resharding oplog applier Created: 19/Oct/20 Updated: 29/Oct/23 Resolved: 26/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2021-05-03 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
after it finishes applying the oplog entry that marks the end of cloning (instead of waiting for applyUntilDone to be called). |
| Comments |
| Comment by Githook User [ 26/Apr/21 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |