[SERVER-75646] Wait for range deletions before dropping collections when removing config server shard Created: 04/Apr/23  Updated: 29/Oct/23  Resolved: 06/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-75096 Locally drop sharded collections from... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-04-17
Participants:

 Description   

As of SERVER-75096, when the config server transitions to dedicated mode, it drops its drained sharded collections locally so it can later be added back without users directly dropping those collections on the config server first. The drop is in the first transitionToDedicatedConfigServer ran after all chunks and databases have been moved away. There may be pending range deletions though, so secondary reads may still be running or stale routers may target those collections with available read concern and expect to at least read orphans. For the same probabilistic guarantees as for normal migrations, we should only locally drop the collections after waiting for all pending range deletions to complete.



 Comments   
Comment by Githook User [ 06/Apr/23 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-75646 Wait for range deletions before dropping collections when removing config server shard
Branch: master
https://github.com/mongodb/mongo/commit/ddc123c781a4d4f15d1ae242c59659c72623d89e

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