[SERVER-75515] Drop all config.cache.* collections during restore procedure Created: 30/Mar/23  Updated: 28/Apr/23  Resolved: 28/Apr/23

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

Type: Task Priority: Major - P3
Reporter: Shin Yee Tan Assignee: Shin Yee Tan
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-68633 Add a check to ensure that new config... Closed
Assigned Teams:
Storage Execution
Backport Requested:
v6.0
Sprint: Execution Team 2023-04-17, Execution Team 2023-05-01
Participants:

 Description   

With optional config servers where we may see shards acting as config servers, we started seeing more config.cache.* collections while running _configsvrRunRestore.

Since it is safe to drop cache collections, we want to drop all config.cache.* unconditionally as clean up on mongod's during the restore procedure.



 Comments   
Comment by Shin Yee Tan [ 28/Apr/23 ]

Closing this ticket because within the sharded cluster hot backups procedure and cloning data into a new sharded cluster, after instructed to run the _configsvrRunRestore command on a standalone mongod, there is already a step to drop all cache collections in the config server.

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