[SERVER-49193] Recover the VectorClock on shard primary step up Created: 30/Jun/20  Updated: 27/Oct/23  Resolved: 18/Aug/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Kaloian Manassiev
Resolution: Gone away Votes: 0
Labels: PM-1645-Milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-50002 ReplicaSetAwareService test should ju... Closed
depends on SERVER-48717 Implement the persist/recover functio... Closed
depends on SERVER-49192 Persist the VectorClock for configTim... Closed
depends on SERVER-49921 Optimize wait for vector clock persis... Closed
Sprint: Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-10, Sharding 2020-08-24
Participants:

 Description   

Call the recovery before a node becomes primary using onStepUpBegin

On secondaries: check if finishRecoveryIfEligible is suited for the purpose (Repurposed, to address in a separate ticket if a use case with secondaries arises)



 Comments   
Comment by Kaloian Manassiev [ 18/Aug/20 ]

Gone away as a result of SERVER-49921.

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