[SERVER-58362] Refactor SSCCL's functions purging cached collection metadata Created: 08/Jul/21  Updated: 29/Oct/23  Resolved: 26/Aug/21

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

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-07-26, Sharding EMEA 2021-08-09, Sharding EMEA 2021-08-23, Sharding EMEA 2021-09-06
Participants:

 Description   

In order to rationalize the code that access the persistent cache managed by SSCCL, the dropChunksIfEpochChanged function can be removed and instead take advantage of the dropChunksAndDeleteCollectionsEntry function. The latter deletes both the collection entity and the chunks collection from the persistent cache, which will be then appropriately recreated later.

This comes from SERVER-34632's code review.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 26/Aug/21 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-58362 Refactor SSCCL's functions purging cached collection metadata
Branch: master
https://github.com/mongodb/mongo/commit/789c686a8c6d5d05f501406d54c611bca1266e6e

Generated at Thu Feb 08 05:44:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.