[SERVER-75093] Consider deleting config.cache documents on config servers during setFCV downgrade Created: 21/Mar/23  Updated: 18/Apr/23  Resolved: 18/Apr/23

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

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Participants:

 Description   

Config servers can accumulate these documents when they become catalog shards. Normally, they would be harmless to keep around. Even if we transition them to dedicated config servers back to catalog shards multiple times, the catalog cache loader logic can handle updating/auto-correcting the cached documents. However, if the collection is dropped while it is in dedicated config server (either in v6.0 or v7.0), these documents can stay there forever.


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