[SERVER-85845] Remove vector clock checkpoint before deleting DDL coordinator documents Created: 29/Jan/24  Updated: 01/Feb/24

Status: Blocked
Project: Core Server
Component/s: Sharding
Affects Version/s: 6.0.9, 7.2.0, 7.0.6
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-85534 Checkpoint the vector clock after com... In Code Review
Related
related to SERVER-61004 Checkpoint the vector clock before re... Closed
Assigned Teams:
Catalog and Routing
Participants:

 Description   

Starting from SERVER-61004 the vector clock is checkpointed before removing DDL coordinator documents. That change was aimed at ensuring causal consistency with the sharding catalog by persisting the config time so that it could be recovered on step-up.

That's not enough because the only way to ensure causal consistency is to persist the vector clock before exiting the critical section (aka before allowing refreshes to hit again the config server). Considering that, we should probably get rid of the changes introduced by SERVER-61004: persisting the vector clock is not an issue, but it's not useful either in that point of the code.


Generated at Thu Feb 08 06:58:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.