[SERVER-70004] Sharded DDL Operations should checkpoint the vector clock during the commit phase Created: 27/Sep/22  Updated: 26/Oct/23

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

Type: Bug Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to SERVER-73389 Checkpoint vector clock in drop datab... Closed
Assigned Teams:
Catalog and Routing
Operating System: ALL
Participants:

 Description   

In a failover scenario it might happen that a new primary steps up but it is not aware of the latest performed DDL operation because it has an old configTime . This can lead us to scenarios like the one described in BF-26346, in which we ended up installing an old filtering metadata.


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