[SERVER-62644] Choose a better name for the VectorClock component Created: 14/Jan/22 Updated: 06/Dec/22 Resolved: 14/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Participants: | |||||||||
| 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:
|