-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-09-21, Sharding 2020-10-05
The getClusterTimeForReplicaSet() function returns a "clusterTime" of 0 if the mongod is not running in a replica set. However, now that the VectorClock is always present, even on standalones and in unittests where it is never ticked/advanced, it should be possible to remove the getClusterTimeForReplicaSet() function and its few uses, and just use the actual VectorClock clusterTime instead (since it should always be 0).
- related to
-
SERVER-48433 Remove LogicalClock facade
- Closed