[SERVER-49921] Optimize wait for vector clock persistence Created: 27/Jul/20 Updated: 29/Oct/23 Resolved: 18/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 2020-08-24 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Add the ability to pass a particular set of components to waitForInMemoryVectorClockToBePersisted that are expected to be persisted up to a certain value. This will avoid to schedule unnecessary tasks on the executor. |
| Comments |
| Comment by Githook User [ 17/Aug/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |
| Comment by Githook User [ 11/Aug/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: It should be in the same library where the commands are included, rather |