Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
Sharding 2020-05-18, Sharding 2020-06-01, Sharding 2020-06-15
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.
Attachments
Issue Links
- causes
-
SERVER-50322 Fix libfuzzertests compile
-
- Closed
-
-
SERVER-51074 VectorClock is not gossiped correctly on newly started sessions
-
- Closed
-
- depends on
-
SERVER-46200 Implement a VectorClockService
-
- Closed
-
-
SERVER-48406 Add onBecomeArbiter to ReplicaSetAwareService
-
- Closed
-
-
SERVER-48534 NetworkTestEnv should not schedule responses for fire-and-forget commands
-
- Closed
-
- is depended on by
-
SERVER-44097 Remove term from config server opTime tracking
-
- Closed
-
-
SERVER-47406 Implement the persistence and tracking of a cluster `topologyTime`
-
- Closed
-
- is related to
-
SERVER-48610 ReplicaSetAwareService callbacks don't occur in ReplicationCoordinatorImpl tests
-
- Closed
-