[SERVER-47914] Move clusterTime from LogicalClock to VectorClock Created: 04/May/20  Updated: 29/Oct/23  Resolved: 05/Jun/20

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

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Kevin Pulo
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-46200 Implement a VectorClockService Closed
depends on SERVER-48406 Add onBecomeArbiter to ReplicaSetAwar... Closed
depends on SERVER-48534 NetworkTestEnv should not schedule re... Closed
is depended on by SERVER-44097 Remove term from config server opTime... Closed
is depended on by SERVER-47406 Implement the persistence and trackin... Closed
Problem/Incident
causes SERVER-50322 Fix libfuzzertests compile Closed
causes SERVER-51074 VectorClock is not gossiped correctly... Closed
Related
is related to SERVER-48610 ReplicaSetAwareService callbacks don'... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-05-18, Sharding 2020-06-01, Sharding 2020-06-15
Participants:

 Description   

The cluster-wide cluster time is currently managed by the LogicalClock class. This should be moved to instead be the ClusterTime component of the VectorClock service, and the LogicalClock class removed.



 Comments   
Comment by Githook User [ 05/Jun/20 ]

Author:

{'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}

Message: SERVER-47914 Move clusterTime from LogicalClock to VectorClock
Branch: master
https://github.com/mongodb/mongo/commit/7074dee1fbf6763c0d463c377c2e47d8ef2c4f6f

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