The VectorClock class serves as the one place where store, maintain and gossip the collection of logical clocks we have in sharding (and by consequence for replica-sets as well).

It has been pointed out that VectorClock is a misnomer, because the clocks are not necessarily independent from each other (there is a ordering relationship between them, where clusterTime >= configOpTime >= topologyTime).

Because of this we should choose a better name.

Some candidates:

• LogicalClock
• LogicalClocks