[SERVER-62646] Choose a better name for the VectorClock component Created: 14/Jan/22  Updated: 26/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-62643 Choose a better name for the VectorCl... Closed
is duplicated by SERVER-62644 Choose a better name for the VectorCl... Closed
is duplicated by SERVER-62645 Choose a better name for the VectorCl... Closed
Assigned Teams:
Catalog and Routing
Participants:
Story Points: 2

 Description   

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

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