[SERVER-74988] Document change stream garbage collection for shard split Created: 17/Mar/23  Updated: 27/Oct/23  Resolved: 24/Apr/23

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

Type: Task Priority: Major - P3
Reporter: Didier Nadeau Assignee: Christopher Caplinger
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Serverless
Sprint: Server Serverless 2023-05-01
Participants:

 Description   

We need to verify if the current steps taken by cloud to garbage collect data at the end of shard split properly clean change streams data and metadata. If they don't garbage collect everything, we need to provide documentation for additional steps.



 Comments   
Comment by Christopher Caplinger [ 24/Apr/23 ]

All changestream-related data (the change collection itself, pre-images, cluster parameters) for a given tenant is now stored in collections in the tenantId-prefixed config DB. As such, all of this data will be cleaned up by cloud on the donor following a successful shard split.

See OrphanTenantDataJob

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