[SERVER-85534] Checkpoint the vector clock after committing shard collection Created: 22/Jan/24 Updated: 06/Feb/24 |
|
| Status: | In Code Review |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.0, 6.0.0, 7.0.0, 7.3.0-rc1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pol Pinol | Assignee: | Jordi Olivares Provencio |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v7.3, v7.0, v6.0, v5.0
|
||||||||||||
| Sprint: | CAR Team 2024-02-05, CAR Team 2024-02-19 | ||||||||||||
| Participants: | |||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
The CreateCollectionCoordinator (both Legacy and v8.0 coordinators) must persist the config time after committing the shard collection to the config server. This will ensure that even in case of stepdown, the next primary, during collection metadata refresh, will read information that is inclusive of the commit. |