[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:
Depends
is depended on by SERVER-53005 Complete TODO listed in SERVER-38918 Backlog
is depended on by SERVER-49193 Recover the VectorClock on shard prim... Closed
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: SERVER-49921 Optimised persistence and recovery of the VectorClock
Branch: master
https://github.com/mongodb/mongo/commit/f37ab825928d30d911f419b9995658866bbe43e4

Comment by Githook User [ 11/Aug/20 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-49921 Pull the `_vectorClockPersist` command out of the 'vector_clock_mongod' library

It should be in the same library where the commands are included, rather
than together with the VectorClock implementation.
Branch: master
https://github.com/mongodb/mongo/commit/0514a0d5286e9c988cbb0fa127220d11932b5883

Generated at Thu Feb 08 05:21:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.