[SERVER-49192] Persist the VectorClock for configTime and topologyTime casual consistency Created: 30/Jun/20  Updated: 29/Oct/23  Resolved: 08/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: Pierlauro Sciarelli
Resolution: Fixed 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-48717 Implement the persist/recover functio... Closed
depends on SERVER-49400 Differenciate VectorClock persist beh... Closed
is depended on by SERVER-49193 Recover the VectorClock on shard prim... Closed
Related
related to SERVER-62243 Wait for vector clock document majori... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-10
Participants:

 Description   
  • Before deleting the MigrationCoordinatorDocument (here)
  • Before writing the TransactionCoordinatorDocument (refer to SERVER-38918)
  • Upon some specific calls to ShardRegistry::reload (repurposed):
    • When a shard is added (here)
    • When a shard is removed (here)


 Comments   
Comment by Githook User [ 08/Aug/20 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-49192 Persist the VectorClock for configTime and topologyTime causal consistency
Branch: master
https://github.com/mongodb/mongo/commit/8da5e4febe5b7d4a055e08f49489f6b22b900abb

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