[SERVER-50998] Remove getClusterTimeForReplicaSet() if possible Created: 17/Sep/20 Updated: 29/Oct/23 Resolved: 17/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Kevin Pulo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2020-09-21, Sharding 2020-10-05 | ||||||||
| Participants: | |||||||||
| Description |
|
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). |
| Comments |
| Comment by Githook User [ 17/Sep/20 ] |
|
Author: {'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}Message: |