[SERVER-77472] Investigate if there are other operations that may not persist config time after a collection drop at migration_util.cpp Created: 25/May/23  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Pol Pinol 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:
Related
related to SERVER-71918 DropCollectionCoordinator must persis... Closed
Assigned Teams:
Catalog and Routing
Sprint: Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18
Participants:

 Description   

When we are sure that all operations persist the config time after a drop collection, we can remove this extra "waitForDurableConfigTime".


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