[SERVER-68212] Disallow existing config.image_collection entry to go from invalid to valid Created: 21/Jul/22  Updated: 05/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Israel Hsu
Resolution: Unresolved Votes: 0
Labels: sharding-nyc-subteam3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-68209 Remove uassert that prevents config.i... Closed
Sprint: Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11, Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5, Cluster Scalability 2024-2-19
Participants:
Story Points: 2

 Description   

SERVER-68209 makes it legal to overwrite an existing config.image_collection entry with lsid, txnNumber and ts by removing this uassert. We should repurpose to removed uassert to fail if the incoming entry doesn't have "invalidated" set to true. This case should never get hit since it shouldn't be possible for an entry to go from invalid to valid.


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